-
Notifications
You must be signed in to change notification settings - Fork 0
Chat Interface
Harness edited this page May 19, 2026
·
5 revisions
The Harness chat is designed like Cursor: messages on top, composer at the bottom, provider pills below the input.
┌─────────────────────────────┐
│ Messages (scroll) │
├─────────────────────────────┤
│ + New chat | Clear context │
│ [ context chips ] │
│ ┌───────────────────── ↑ ┐ │
│ │ Ask anything… │ │
│ └───────────────────────┘ │
│ Ask | Agent | Spec+Agent │
│ Copilot | Claude | … ⚙ │
└─────────────────────────────┘
| Button | Action |
|---|---|
| + New chat | Clears conversation history, new session ID, clears input |
| Clear context | Removes all context files and clears the input text |
| ↑ | Send (Ctrl+Enter). Becomes ■ while streaming (stop) |
Click a provider to switch: Copilot, Devin, Cursor, Claude, Kiro.
The selected pill is highlighted. Changing provider applies to the next message.
| Mode | Description |
|---|---|
| Ask | Conversational Q&A (Copilot SSE streaming) |
| Agent | Autonomous tool loop (read/write files) |
| Spec+Agent | Agent + active Spec YAML as system context |
Copilot modes only apply when Copilot is selected. See Copilot Modes.
When the agent mentions files like `src/app.ts:42`, they appear as clickable links. Click to open the file at that line in the editor.
Context chips also open files on click (× removes from context).
| Command | Effect |
|---|---|
/clear |
Clear conversation (webview only) |
/agent copilot |
Switch provider |
View → Output → Harness — full IPC trace (secrets redacted). Use for debugging daemon issues.
Getting started
Using Todd of AIDLC
Agents
Advanced
Help