Run an agent in a terminal

The terminal in LogiShell is not "run a command and show the output". It is a real login shell ($SHELL -l in a PTY) on the machine, drawn by xterm.js in a tab. Colour, arrow keys, history and tmux work, because there is nothing to emulate.

That matters most for agents. Claude Code, Codex and the Gemini CLI are interactive programs, and the expensive part of working with them is not the model, it is the warm context.

Open one

You need a connected machine and a project on it. Open the project, then the terminal panel at the bottom.

• ⌘D opens another shell next to the current one. It is a new session, not a second view of the same one: two screens sharing one PTY would split your typing.
• The tab names itself after the work. Your own name wins; otherwise the first meaningful command does it (pnpm build becomes "Build"), and only then a number. Hover and wait to see three lines of what is happening in there; hold ⌘ for the whole card.

Then start your agent the way you normally do: claude, codex, gemini. LogiShell does not proxy the model and does not read those credentials. The shells the IDE opens do not inherit the runner's own credentials either.

Close the tab, keep the agent

The session belongs to the runner on the machine, not to the browser tab. Closing the tab does not kill the shell. It keeps running, its output is written to disk, and it survives a page reload, a jump to "All projects", a dropped network, and even a restart of the runner itself.

To come back: the shelf of shells, Attach (⌃⇧T or ⇧⌘T).

Continue a conversation instead of paying for it twice

An hour of conversation in which the model has finally understood your project is worth tens of thousands of tokens. Starting fresh means buying that again.

Journal → Sessions lists the Claude Code and Codex sessions found on the machine, each with the size of its live context, taken from the agents' own files rather than estimated. Continue brings that exact conversation back up (claude --resume, codex resume) in a new terminal tab.

The two agents report differently, and the page does not pretend otherwise. Codex knows its context window, so the line reads 117.4k of 258.4k context. Claude Code does not report a window, so it reads 325.3k context and no percentage, because a percentage with an unknown denominator is a guess.

Let LOG watch it

LOG can see the terminals and say something when it matters: a run has been waiting for more than two minutes, something failed in the tail, an agent finished writing in a tab you are not looking at. It repeats no more than once every ten minutes, and there is a switch to turn it off.

Writing into a terminal is a different thing from watching one. It goes through the consent gate every time: a request names the exact machine, project, session, action and input, lands in your inbox, and only an approved request executes, once.

When it does not work

• Arrow keys, Backspace or colour misbehave. That was one bug with one cause: a PTY started by a GUI parent without TERM. The session declares TERM=xterm-256color itself now. If you see it again, it is a new bug and worth reporting.
• The tab is gone but the work was not finished. It almost certainly is not gone. Look in the shelf and Attach.
• The machine went to sleep. The session is on that hardware. Wake the machine; Device Center says when it last checked in.

Next: show someone that it works.