Workspace plugins

简体中文

Workspace services can be composed independently of the Agent engine. Each leaf declaration selects a native provider, while UI consumers bind the contracts they need.

• Files uses the file engine and pure patch parser.
• Processes owns commands, terminals and protocol processes.
• Web provides fetch and search; its API crate contains the declarations.
• Jev exposes the structured evaluation engine.
• Computer Use exposes cua_repl and cua_reset through the native provider. Each conversation needs explicit access approval. Changing its permission boundary invalidates that grant; Explore mode cannot operate the computer. REPL variables and target bindings last until reset or Host shutdown, while the conversation grant survives restart. Desktop and browser connections are selected in the provider configuration.

The shared API defines workspace contracts. Support handles configured roots, directory selection and private-path exclusions. A service receives its resource limits and authority explicitly; a path in request JSON cannot widen them.