First conversation

Point Shrevix at a repository, ask for a change, and approve your first diff — this takes about two minutes. Here’s the whole flow, end to end:

The live conversation keeps reasoning, tools, task progress, final output, and reply controls in one workbench.

1. Pick a model and a workspace

Look at the bottom of the composer. Two pickers matter right now:

• the model — new chats use signed-in Codex Local · GPT-5.6 Sol by default; choose another configured provider or model in Models & keys when this task calls for it.
• the workspace — the repository or worktree used by the turn. Built-in file tools are confined to this root. Shell commands use the configured containment backend when available; host execution requires explicit opt-in and is not an operating-system sandbox. A primary Build session with Bypass enabled deliberately removes the workspace boundary; see Approvals & modes.

The dashboard composer can start the conversation with its agent, model, mode, reasoning, and workspace already selected.

2. Ask for something real

1. Type a concrete task — implement a login form and run the build works better than “help me with auth”.
2. Press Enter. Shrevix picks the capabilities it needs — reading files, searching code, running commands — and shows every step as it goes.
3. Watch the tool calls stream in. Nothing is hidden: every file read, every search, every command is a visible row in the transcript, with its result summarized underneath. For anything multi-step, a task list appears too and checks off as the agent works — you always know which step it’s on.

The conversation remains open as another browser-style tab while you inspect its workspace diff.

Tip

Not ready to let it edit files or run shell commands? Toggle Plan in the composer. Those local mutations are blocked while the agent investigates and proposes. A separately configured MCP autoApprove policy can still permit its allowlisted tools, so review server policy before relying on Plan for external systems.

3. Approve the diff

With Bypass permissions off (the default), a requested file change stops at the tool call. You get the full diff and a permission card; that write is not applied until you approve it. Enabling Bypass under Settings → Agent & runtime deliberately removes this pause for Build turns.

• Approve applies exactly the change you saw.
• Deny rejects it; tell the agent what to do differently and it adjusts.

write filesrc/auth.tswaiting for approval

- return refresh(token)+ if (token.expiresSoon()) refresh(token) return token

ApproveDeny

The write tool keeps its code diff inside the approval event.

Note

The same gate applies to shell commands and, by default, MCP tool calls. Read more in Approvals & modes.

4. Keep going

The run streams live — and you stay in control. Type and send another message while the agent works to add guidance to the active turn. Leave the input empty to reveal the Stop button when you need to interrupt instead. When the task is done, the conversation stays as a resumable session on your dashboard, and the work sits on the workspace’s branch, ready to review and merge.