Before the first request
You need Rudr installed, access to a coding provider, and a local folder for the task. A subscription that works in one provider does not unlock every other harness. Chat, voice, and image generation can require separate API connections.
- Complete Rudr’s onboarding screens. Review preferences and the security/keychain explanation; configure provider keys only for API features you intend to use.
- Open Settings → Code Harnesses. Select your harness and finish its installation and sign-in steps. For API routes, configure the matching connection under Models.
- Check the displayed readiness and available models, then choose Save settings. Installation alone is not readiness.
- Open Code in the sidebar and start a new session. Choose Open folder or Open folder… and select the working folder.
- Open the model/effort control in the composer. Check the harness, model, and permission mode. Begin with Ask when your harness offers it.
- Send a bounded first request, such as asking the agent to explain the project’s entry points before making changes.
Review the result
The task should show activity in the transcript and eventually a response or an explicit request for approval. Expand tool output when you need evidence behind a claim. Add Files or Git through Add a panel to inspect any changes; the final answer alone does not prove tests passed or files were saved.
If the run fails before beginning, check authentication and readiness. If it is waiting for your decision, answer the visible approval or question rather than starting a duplicate task. Continue with permissions and reading activity.