Let agents operate Code Overlord
On this page
Ask a supported agent to manage sessions, open files, organise notes or schedule work using the app's tools.
Before you start
Launch the agent from the intended Code Overlord workspace. Its local MCP connection provides the app tools. External cloud connectors expose a narrower surface and should not be assumed to control desktop sessions.
Give the agent a bounded task
- Ask the agent to discover the available Code Overlord tools for the task.
- Specify the workspace and the intended action in ordinary language.
- Let it inspect the relevant sessions, files or notes before making changes.
- Have it report the resulting session, file or scheduled task so you can verify it in the UI.
Example instructions
The recorded demonstration uses an existing report in the Ember Studio example workspace:
Discover the available Code Overlord tools and list this workspace's sessions. Open workspace-app-context.md in Peruse and read it. Inspect Thy Quill, then add exactly one note: Studio review: confirm the app and website describe the same saved-search behaviour. Preserve existing notes and reuse that exact note if it already exists. Read the result back and report its note ID and workspace. Keep the existing files unchanged.
Check the actual report in Peruse and both notes in Thy Quill. The recording also shows a follow-up instruction to leave the report visible. Its local session listing succeeds; remote session inventory is unavailable in that run. The report is existing material, so reading it does not constitute a new code review.
List the active sessions in this workspace and summarise which ones need my input.
Open docs/review-notes.md in the file viewer, then summarise its outstanding review points.
Create a weekday task that summarises new Jira blockers for this workspace. Use the configured agent and notify me on failure. Show me the saved schedule and prompt afterwards.
Session discovery, opening files, notepad actions and scheduling are distinct tool capabilities. The agent should use the available schema rather than invent a tool name or assume the same commands as Orca's CLI.
Reuse a workflow
Save a repeatable role as a Minion with clear operating instructions. Use a Ritual for recurring execution. Provider-native skills can carry additional reusable guidance when that CLI supports them. These mechanisms do not require an Orca-style CLI wrapper.
Inspect the app and browser
For websites, configure Browser Automation and follow Fix a UI with browser feedback.
General interaction with unrelated desktop applications needs a separately configured compatible computer-use tool. Check its supported operating system, permissions and actions before relying on it. Code Overlord's documented local MCP surface does not establish a bundled equivalent to Orca's general native computer-use helpers.
Check the result
Verify the actual object in the app: a new session, an opened file, a completed note or a saved Ritual. If the agent only has the public cloud notepad connector, use the local desktop-launched session for broader controls.
More detail
MCP Tools and local/cloud differences · Connect tools · Scheduling