jevieDocs Download

↑↓ pick↵ openesc close

Your coding agents

Coding-agent sessions

See and steer every coding agent you run, Claude Code, Codex and the rest, from one place: what each is doing, which need you, and their questions answered from anywhere.

FreeMacPhoneCoding agent

Jevie’s palette, as the app draws it. Press a sentence on this page to see it, and to copy it.

What it looks likeUse itHow it worksLimitsWhere it's kept

Use it

See them all

Answer and steer

Review its changes

Hand off work

Settings

How it works

Every session Jevie starts lands in Jevie Studio, on its Terminal: terminals as tiles that zoom, dock, tab and lay themselves out, keyed like a tiling window manager. A session that finishes or asks for you takes the biggest tile, so the most recent work is always in front.

Claude Code and Codex are followed turn by turn, and every other agent (pi, OpenCode, Gemini CLI, Cursor, Copilot, Amp, Aider and more) while it runs in a terminal. A permission or a question becomes one card on your Mac and phone with its risk shown; answered in one place, it closes everywhere. Anything that cannot be undone takes a hold to allow and is never always allowed.

A worktree starts ready to work in. The main checkout's untracked .env files are copied in (never over a file already there), then the repository's line in ~/.jevie/self/worktrees.md (- jevie → npm ci) runs in the new worktree, its folder or its folder's name, then a shell command. It may take five minutes; a command that fails or runs out of time never stops the worktree, and how it ended, with the last of its output, comes back with it.

A session started in the background that goes quiet for ten minutes (an hour while one of its commands is still running; never while sub-agents it handed work to are running) is asked to stop and, if it does not, closed; its row says how long it was quiet. One cut off because Jevie itself closed says so, instead of showing the turn before as current. An agent's checklist shows as its step: Todo 2/5 · Fixing the tests.

A session's card in the launcher shows the pictures its latest turn saw (screenshots, pages, images it read) as a strip along its foot. Rest the pointer on one and it shows large in the preview pane beside the list; move off and the pane shows the session again.

Jevie finds your agents where your own shell does: once at start it asks your login shell for its PATH, so an agent installed with nvm, mise, fnm, pnpm or nix is found even when Jevie was started by the Mac and not from a terminal.

Each Claude Code turn is recorded as the files saw it: when the turn starts and when it ends, the working folder is written to git as a tree, through a copy of the index, so your own index, branches and commits are never touched. That is what Last turn compares. Undo only works on a finished turn, and only while its files are still as it left them: if you or another session changed them since, nothing is touched and it says so.

The agent still remembers the turn, so tell it what to do instead. The last 20 turns per session are kept in ~/.jevie/turns.

ai usage reads the same figures as they are now, with no model call: Claude's from its status line (the five-hour window shows 0% once its reset has passed), Codex's from codex app-server (its newest session file when the program does not answer). Only the coding agents: Jevie Cloud's credits are under my plan. A bar turns amber at 70% and red at 90%.

A session cut off by a restart comes back as it was started (resume my sessions): a Claude Code or Codex session keeps the flags it began with (its permissions, model, added folders, Jevie's connection), never its first message again. A Codex session is found by the conversation file its process holds open, so after /new it is the new conversation that comes back.

When an agent runs out of usage, Jevie says so once, with the time it can work again, and new work goes to another signed-in agent until then (hand this session to codex moves the work). For Claude the time is the plan's own: Claude Code's status line reports how much of the five-hour and seven-day windows is used and when each resets, and a window at 100% means Claude waits until that reset. Other agents, and Claude before its status line has said anything, are judged by a reply that says the limit was reached, counted as five hours.

Limits

Where it's kept

Hooks in ~/.claude/settings.json (merged, never replacing yours); live state in the daemon. Worktrees beside the repository in <repo>-wt/.

What it looks like

An agent asking: its question as a card, answered in one tap
An agent asking: its question as a card, answered in one tap
A session followed live, step by step
A session followed live, step by step
Everything at work: what is running and what needs you, Deny or Allow
Everything at work: what is running and what needs you, Deny or Allow

Drawn by Jevie's own renderer with made-up data.

In Jevie, help session answers from this page as you type.

Updated 9 November 2026 · Something wrong or missing? Tell us