How plans are created
Planning is explicit. CodeRabbit Agent starts a planning workflow when you use one of these entry points:- Type
/plan <task description>in a channel. - Type
/planwith no text to open the Plan Changes modal. - Use the Plan this work message shortcut on a Slack message.
- Click Plan this work on a planning offer from CodeRabbit Agent.
#backend-eng, an engineer can type:
Slash commands are available in channels, not in Direct Messages or threads. Use the message shortcut or a planning offer when you want to start from an existing Slack message.
Planning process
CodeRabbit posts an initial implementation plan in the Slack thread, covering the likely change area, key tasks, and open risks. Select Dive deeper to refine the plan with additional codebase research. CodeRabbit saves the result and adds an Open Plan link back to the thread. You can hand the plan off to CodeRabbit Agent for implementation at any point, or stop planning and switch to implementation straight away.Review and handoff
Open saved plans from Slack or from the web app. Saved plans preserve the research, assumptions, phases, tasks, summary, and version history for the work. Use the Slack action buttons to hand either the first-pass plan or the saved plan back to CodeRabbit Agent for implementation.Relationship to CodeRabbit Plan
CodeRabbit Agent planning builds on the broader CodeRabbit planning model. Coding Plans created from Slack appear alongside plans created from the web app or issue trackers. For the canonical product docs covering plan structure, refinement, and agent handoff, see CodeRabbit Plan.What’s next
Working in Slack
See how
/plan starts from Slack and when that work moves into the web UI.CodeRabbit Plan overview
Read the canonical planning docs for plan structure, refinement, and handoff behavior across CodeRabbit.
Thread reviews
Inspect the run history behind a planning conversation when you need more context than the final plan alone.