Feature Mode
Describe what you need. The agent builds it — action-first, no planning required.
Describe what you need. The agent builds it.
Feature mode is built for one thing: getting from idea to working code as fast as possible. There's no planning phase, no approval step — the agent reads your request and starts coding immediately.
What it does
Feature mode is action-first. The agent reads your task description, locates the relevant parts of your codebase, and begins implementing. Progress streams live to the sidebar as work happens, so you always know where things stand.
Each Feature conversation runs in its own isolated branch, so your main codebase is never touched until you decide to merge.
When to use it
- Adding a new component, screen, or UI element
- Integrating a new API or third-party service
- Implementing a spec that's already been scoped
- Adding a new command, endpoint, or data model
- Any task where you know what you want built
If you're not sure how to implement something — only what you want — Feature mode handles the how. The more context you give, the better the result.
How it works
- Write your task — describe the feature in plain language. Be specific: what should be built, where it fits, any relevant constraints.
- Attach context — use
@to reference files, folders, or docs the agent should know about. - Send — the agent starts immediately. No plan to approve, no questions to answer.
- Follow progress — the sidebar shows each step: files being read, code being written, checks running.
- Review and merge — when done, open the diff viewer to see all changes. Merge when satisfied, or send a follow-up to refine.
Key features
- Action-first — no plan approval required; the agent starts coding on the first message
- Isolated branch — work happens in a dedicated Git branch; your main codebase is untouched
- Live sidebar — see step-by-step progress as the agent works through the task
- Auto model selection — the system picks the optimal model for the task complexity
- Continuable — send follow-up messages in the same conversation to refine or extend the work
Tips
Be specific about inputs and outputs. "Add a button that calls the /api/export endpoint and downloads a CSV" gets better results than "Add an export feature."
Attach relevant files with @. If you want the agent to match your existing component style, attach a similar component. Rich context leads to better-fitting code.