Chat
The thread is where a task starts and where its record stays. It carries plans, tool calls, approvals and the files involved.
Threads that hold the work
A conversation keeps the plan, the diffs, the approvals and the artifacts it produced, instead of scattering them across messages.
Learn moreSlash commands and skills
Named commands run repeatable work from the composer, with the same permission rules as anything else.
Learn moreProvider system
Local runtimes, your own keys, an existing subscription, and routing rules for when one is unavailable.
Learn more
Agents
Agents are named, scoped and reviewable. They carry their own tools and their own gates rather than inheriting everything.
Agent teams
Several agents on one task, each with a role, with a lead that reviews before work merges.
Learn moreUnified execution
One execution path for built-in and external agents, so behaviour does not change with the backend.
Learn moreExternal agents
Run agent backends you already use, hosted by the workspace rather than replaced by it.
Learn more
Knowledge
What the workspace remembers between tasks, where each piece came from, and how to remove it.
Long-term memory
Durable notes with their source attached, surfaced when a task needs them rather than injected everywhere.
Learn moreKnowledge capture
Bring in pages, documents and screenshots, and keep the extraction next to the original.
Learn moreLocal storage and search
Where the workspace keeps things on disk, and how search reaches them.
Learn more
Desktop
The parts that only exist because the workspace runs on your machine.
Integrated terminal
Run the command, keep the output attached to the task that needed it.
Learn moreEditor and Pro IDE
Read and edit project files in place, with a full editor when the change is bigger than a diff.
Learn moreSource control
Stage, review and commit from the workspace, with the diff the agent produced in front of you.
Learn more
The systems behind the visible workbench.
Chat is only the entry point. Context, interactive surfaces, connected conversations, and durable automation keep the work moving after the first reply.
Context workbench
Assemble project files, captured resources, instructions, and prior artifacts into the exact context a task may use, without expanding every prompt by default.
Files · resources · instructions
Learn moreCanvas and interactive apps
Turn model output into editable artifacts, visual canvases, and A2UI interfaces whose state and interactions remain part of the task record.
Canvas · A2UI · artifacts
Learn moreConnected inbox
Bring Slack, Lark, Discord, Telegram, Matrix, and other adapter conversations into one inbox with explicit inbound and outbound policies.
Inbox · adapters · dispatch rules
Learn moreSchedules and durable goals
Run recurring work while the desktop app is minimized, retain its history, and let longer objectives continue through reviewable steps.
Scheduler · goals · run history
Learn more