connect DEV to live MCP configuration and verify tool conformance

This commit is contained in:
2026-09-29 10:36:50 +01:00
parent 20bbbd26bd
commit 9592c9b274
16 changed files with 417 additions and 18 deletions
+34 -1
View File
@@ -21,14 +21,47 @@ The root project is a monorepo with these main areas:
## Current Product Shape
The Studio shell currently organizes the product around three workspaces:
The Studio shell currently organizes the product around four workspaces:
- Assets
- Debug
- DEV (external-agent authorization and observation)
- Shipper
At runtime, the app boots an embedded packer, restores project-local Studio state, and opens the Studio launcher window. Project creation currently scaffolds a Prometeu workspace with `prometeu.json`, `src/`, `assets/`, `build/`, `cartridge/`, `.workspace/`, and local Studio metadata.
## External Coding Agents (MCP)
Open a project and select **DEV → Copy MCP configuration**. The copied JSON is a
provider-neutral connection descriptor: use its `url` and `headers.Authorization`
in your external client's Streamable HTTP MCP setup, and provide its `projectRoot`
and instructions to the agent. Adapt the configuration syntax to your client;
there is no embedded chat or provider-specific setup wizard.
Keep the descriptor/token private and out of versioned files and logs. The endpoint
is local to this computer. After restarting Studio, copy it again and update the
client: both the port and token are ephemeral. Copying or connecting does not
authorize edits or start a task.
1. Connect, discover tools, read project context and applicable language/SDK references.
2. In DEV, grant control (save all first if prompted). Active Debug prevents granting.
3. The agent acquires a task, edits saved project files using its own tools, and
validates through LSP/build. SDK and external libraries are consultable, read-only.
4. Poll operations by operationId or clientRequestId. Recover a lost start receipt
by lookup; never retry frame advancement blindly with a new ID.
5. The agent explicitly releases control. To interrupt, use DEV's reclaim button
and stop the external client separately: Studio cannot prevent its direct file writes.
The current production tools cover context, references, task control, LSP,
build/pack and operation lookup/cancellation. Headless tool handlers are tested,
but remain undiscoverable until the real runtime gateway is composed. DEV is an
observation panel, not manual Play/input for the agent's session; **Debug** retains
the human testing workflow. Edits are preserved on cancellation; Git/review/recovery
remain the developer's responsibility.
See the [MCP contract](docs/specs/studio/11.%20MCP%20Tools%20and%20Project%20Knowledge%20Contract.md)
for schemas, authorization, limits and delivery boundaries.
## Requirements
- JDK 21 or newer recommended for local development