Choose the right surface
Code runs a coding harness against a folder. A harness is the integration that executes the task: for example, Claude Code or Codex. It determines available permission modes, tools, and native session features. The model and access route are separate choices.
Chat is a conversation with a configured model. Its API connection is separate from an external coding CLI subscription. Side chat lets you discuss a Code task in its workspace and is presented as read-only.
Rudr is the application. Rudr Code is its built-in, pre-alpha coding harness. Choosing Rudr does not require choosing Rudr Code.
Bring existing work
- Set up an enabled harness in Settings → Code Harnesses.
- Open Code, then choose a folder for the task.
- Select a model and permission mode in the composer before sending your request.
- Add Files, Terminal, Git, Browser, or Side chat panels to review the work alongside the transcript.
Your selected folder is the working directory. A Chat project organizes conversations; a Git worktree provides a separate checkout. Neither should be confused with a provider account.
Keep work moving
Rudr retains sessions so you can return to them, reference another session, or import supported local tool histories. Existing-session provider continuation is limited to Claude Code ↔ Codex between runs. It creates a linked destination with bounded context; it does not move a running process or transfer all provider memory.
Start with your first task, compare access routes, or read continuation limits.