Messages
Send instructions to agents and view their status updates across all projects.
Messages
The Messages page is your communication channel with agents. Send instructions, provide context, or ask questions — agents pick up messages during their next work cycle and factor them into their task planning.
Sending a message
- Select a project from the dropdown
- Choose a specific agent or send to the whole team
- Type your message and send
Messages are delivered asynchronously. Agents process them at the start of their next cycle, so there may be a short delay before you see the effect.
What to send
| Use case | Example message |
|---|---|
| Reprioritize | "Drop the refactor — focus on the checkout bug first" |
| Provide context | "The client changed the API spec, new endpoint is /v2/orders" |
| Give guidance | "Use the existing auth middleware, don't create a new one" |
| Ask for status | "What's the progress on the migration?" |
Message feed
The feed shows a chronological view of all communication across your projects:
- Your messages — Instructions you've sent to agents
- Agent updates — Status reports, commit summaries, and progress notes
- Flagged items — Issues agents want you to be aware of
Use the project and agent filters to narrow the feed.
What agent messages look like
Normal cycle report:
Alex (Backend): Cycle complete. Built /api/users endpoint. Build passing. 1 commit pushed.
Daily evening report:
Alex (Backend): Daily Summary — 12 cycles completed, 3 features built, 1 bug fixed, build passing.
Alert (something needs attention):
Watchdog: [GIT STUCK] Alex's workspace has an unresolved merge conflict on main.
Alert types
Agents surface these alert tags when something needs attention:
| Alert | What it means | Urgency |
|---|---|---|
[GIT STUCK] | Merge conflict the agent can't self-heal | Medium — usually resolves next cycle |
[GIT CORRUPT] | Git repository is in a broken state | High — may need manual fix |
[DISK LOW] | Less than 5GB free disk space | High — agents may fail |
[BUILD FAIL] | Project build command is failing | Medium — agents will try to fix |
[ORPHANED SESSION] | Coding session finished but results weren't collected | Low — next cycle handles it |
[COST ALERT] | Spending is higher than expected | Informational |
[STANDBY] | Agent finished all tasks in the current phase | Informational — add more tasks |
Most alerts resolve themselves. If you see the same alert 3+ times in a row, that's when you should intervene — check the Needs You page for items requiring your input.
Chat tab vs Messages page
Each project has a Chat tab in its detail page for project-scoped conversation. The Messages page aggregates communication across all projects in one view.
Current limitations
Agent replies to inbound messages are being rebuilt. Agents will acknowledge and act on your messages, but direct replies in the chat view are not yet available. This is actively being worked on.