Skip to content

Chat

The Chat view is where you interact with the AI agent. It occupies the main area of every thread. The agent can read and write files, run shell commands, search the codebase, and ask you questions — all scoped to the thread’s isolated directory.

Type in the chat input at the bottom of the screen and press Enter (or Cmd+Enter / Ctrl+Enter) to send.

Type # in the input to open an autocomplete dropdown of files in the thread’s directory. Select a file to insert a reference like #src/components/Button.tsx. The agent will read that file as context for your message.

If the agent is still processing a previous message when you send a new one, the new message is queued and sent automatically when the current response completes. A queue indicator appears in the input area. This lets you compose follow-up messages without waiting.

Agent responses stream in real time. You can read the response as it’s being generated. The chat area shows:

  • Text responses — rendered as Markdown (code blocks, headers, lists, inline code, etc.)
  • Tool call indicators — inline status tags showing which tool the agent is using (e.g. read, write, bash, grep)
  • ask_user blocks — if the agent needs clarification mid-run, it pauses and shows a question with a response input (see below)

The agent has access to these built-in tools:

ToolWhat it does
readRead a file (up to 2000 lines / 512 KB)
writeWrite or create a file (creates parent directories)
editExact find-and-replace within a file
bashRun a shell command in the thread directory
grepRegex search across files (powered by ripgrep)
findFind files by glob pattern (ignores node_modules, .git)
lsList directory contents
execute_skill_scriptRun a script from an active skill’s scripts/ directory
read_skill_referenceRead a file from an active skill’s references/ directory
ask_userPause and ask you a question before continuing

All file and shell operations are sandboxed to the thread’s directory. The agent cannot read or write files outside it.

When the agent encounters an ambiguous decision, it can use the ask_user tool to pause and show you a question:

“Should I replace the entire auth module or just add the new endpoint alongside the existing one?”

An input block appears in the chat. Type your answer and press Enter to let the agent continue. This keeps you in the loop on consequential decisions without interrupting trivial steps.

Toggle Plan Mode using the button to the left of the input field (or the keyboard shortcut). In Plan Mode the agent focuses on producing a structured plan for your request rather than immediately making changes. Useful for:

  • Understanding the scope of a task before committing to it
  • Reviewing a proposed approach and asking for adjustments
  • Exploring multiple strategies before picking one

Disable Plan Mode to switch back to the default action-first behaviour.

Each thread has an independently selected model. Click the model selector dropdown in the top-right of the toolbar to change the model for the current thread without affecting other threads.

Only models that have been enabled in Providers & Models settings appear here. See Providers Overview for the full list of available providers and models.

The chat input includes a microphone button. Click it to use your browser’s or system’s speech recognition to dictate a message. The transcribed text is inserted into the input field before sending.

Click New Chat (or use the keyboard shortcut) to start a fresh conversation in the same thread. This generates a new conversation ID and clears the visible chat, but all previous messages are preserved in the conversation history. See Conversation History for details.

ActionShortcut
Send messageEnter or Cmd+Enter
New line in inputShift+Enter
New conversationCmd+K