Skip to main content
Docs

Search documentation

0 articles

    Contents

    The editor and Agent RX

    Mandarin combines direct editing with an Agent RX workbench. Think of the agent as a request-and-review path alongside your buffers, not as the owner of every action in the editor.

    The objects in a turn​

    A workspace root identifies the project. Open buffers contain working text, which may differ from disk. A draft contains words you can still edit. Submitting that draft starts or queues a request. Tool traces show attempted operations and returned evidence. A proposal describes a possible change; accepting it changes a buffer, and saving persists that buffer.

    These stages answer different questions. A completed response says the model turn ended; it does not prove that all proposed hunks were accepted, that the file was saved, or that the project passed its checks. A manually entered terminal command is direct shell work and does not wait for proposal acceptance.

    Workspace and queue boundaries​

    Check the displayed workspace root before asking for inspection. Keep code in project files and request targeted reads instead of pasting the entire repository. Suggestion chips fill the editable draft rather than sending it automatically. Enter sends or queues the request; Stop cancels the active turn.

    Switching folders changes context, cancels the old worker, and discards its queued requests and review cards. Preserve needed work before switching; an empty new workspace queue is not evidence that old queued requests ran.

    Choose a model route deliberately​

    Use local and Use cloud are available while idle with an empty queue. Local mode requires a compatible local server and does not silently fall back to cloud on failure. Cloud has a separate configuration and processing boundary. Opening the panel proves neither route is connected.

    The standalone Agent RX product shares foundations but has different runtime controls. Do not transfer CLI slash commands or permissions into the editor by analogy. See privacy and permissions before sharing project content or diagnostic output.

    Continue with draft, send, queue and stop, or compare local and cloud routes before submitting sensitive project context.