Repository navigation
Description
Parent roadmap #261. Relates to #33.
Goal and scope
Let users select Cursor as an Agent runtime in OpenDirector, use their Cursor account and models, and create or edit project content through the shared business commands.
User flow and rules
- Detect Cursor Agent CLI and provide installation or authentication guidance when unavailable. Reuse Cursor authentication.
- Offer model selection and preserve supported reasoning settings per conversation. Determine available controls from the supported CLI and model.
- Stream replies and tool activity into the conversation. Persist native session identity and resume with incremental input.
- Keep a consistent execution directory across turns and isolate conversations and projects, including after application restart.
- Expose OpenDirector CLI commands and skills through the existing discovery mechanisms. Apply the same revisions, locks, validation, and receipts as other runtimes.
- Pass supported attachments and project references to Cursor. Report unsupported inputs explicitly.
- Stop the local runtime operation and report its actual outcome. Already accepted generation jobs retain their own cancellation and recovery semantics.
- Provide English and Chinese setup, status, and error messages.
Feasibility and integration
Cursor documents an ACP server over stdio for custom clients. The inspected CLI, version 2026.03.30-a5d3e17, exposes agent acp, headless stream-JSON output, partial text output, model selection, and explicit session resume. These capabilities provide an integration starting point. Real OpenDirector tool execution, session recovery, cancellation, image input, and reasoning controls still require validation.
Evaluate ACP first against the existing runtime adapter boundary. Reuse conversation storage, execution directories, command transport, skills, and trace presentation. Map Cursor events to shared reply and tool states and retain raw events for diagnosis. Scope credentials and permissions to the runtime invocation.
Acceptance criteria
- Select Cursor and an available model, then complete a streamed conversation. Missing CLI, authentication failure, and unsupported versions produce actionable messages.
- Ask Cursor to create a text node through OpenDirector CLI. Verify its stored content, object revision, and command receipt.
- Edit the node through the UI, then ask Cursor to read and update it in the same conversation. Verify that the latest user changes are preserved.
- Resume after application restart and verify context retention, a consistent execution directory, and isolation between conversations and projects.
- Stop a running turn and continue without orphan processes, duplicate replies, or automatic resubmission of accepted work.
- Verify tool events and traces against actual command results, using the same status and color conventions as other runtimes.
- Verify supported image inputs with a real multimodal request and preserve selected model and supported reasoning settings.
- Check English and Chinese setup and failure flows. Include CLI version, reproducible checks, actual project results, and UI screenshots in the implementation PR.
Activity