Skip to content

Chat Interface

The chat interface is where you interact with your AI agent. Understanding its features helps you work more effectively.

The chat interface consists of:

  • Message History - Scrollable conversation with the agent
  • Input Area - Where you type messages and commands
  • Session Info - Header showing session details and status

Type your message in the input area and press Enter or click Send. You can:

  • Ask questions about code
  • Request changes or new features
  • Share error messages for debugging
  • Provide feedback on agent outputs

For longer messages, use Shift+Enter for new lines within your message.

Agent responses can include:

Explanations, analysis, and conversational replies appear as formatted text with syntax highlighting for code snippets.

When the agent takes action, you’ll see tool call visualizations:

$ npm install lodash

Shows the command executed and its output.

Read - Displays the file being read with syntax highlighting

Write - Shows the new file content being created

Edit - Highlights the specific changes being made to existing files

Glob - Shows file patterns being searched

Grep - Displays search patterns and matching results

Sometimes the agent offers structured options for next steps. Click a suggested action to send it as your next message.

The interface updates in real-time as the agent works:

  • See commands as they execute
  • Watch files being read and written
  • Monitor long-running operations
  • Receive streaming text responses

Agents can produce artifacts during a session:

  • Code files - New or modified source files
  • Documentation - Generated README or docs
  • Reports - Analysis summaries or audit reports

Access artifacts from the session header menu.

Instead of:

“Fix the bug”

Try:

“Fix the TypeError on line 45 of utils.ts - the user object can be null but we’re accessing .name without checking”

Share relevant information:

  • Error messages and stack traces
  • Expected vs. actual behavior
  • Related files or dependencies

Use follow-up messages to refine:

  • “That’s close, but also handle the edge case where…”
  • “Good, now add error handling for…”
  • “Can you explain why you chose this approach?”

Always review changes before the agent applies them:

  • Read the proposed code changes
  • Understand the approach
  • Ask questions if something seems wrong
ShortcutAction
EnterSend message
Shift+EnterNew line in message
EscapeClear input