Skip to main content
External Apps can permanently delete the archived agents they own.

Summary

An External App can permanently delete an archived agent it owns, exactly as the Console’s second remove does. No new scope: the route uses the opt-in agents:manage scope, decided at the agent’s home.

New

  • DELETE /api/v2/agents/deletePermanently deletes an archived agent the calling External App owns, with agents:manage held at the agent’s home, and purges its channel memory and home-namespace knowledge. Any other agent is 409 conflict with nothing written. Version rows stay as audit records and published workflow versions keep their pins. A recorded result is never replayed: read the agent to learn an attempt’s outcome. See Permanent deletion.
  • Forge MCP adds forge_delete_agent_permanently in the agents group (211 tools).

Changed

  • DELETE /api/v2/agents/delete and forge_delete_agent still archive; their text now names the permanent delete instead of saying it is Console-only.
Publishing an agent for public A2A discovery stays in the Console.
Primitive versions, consumers and agent rollback for machine credentials.

Summary

Machine credentials can list an agent’s or a tool’s immutable versions, see which published workflow versions pin an agent or a procedure before changing it, and, for an agent an External App owns, roll its active version back. No new scope: the reads use agents:read, tools:read and procedures:read, and the rollback uses agents:manage.

New

  • GET /api/v2/agents/listVersions and GET /api/v2/tools/listVersions list versions newest first, identity fields only (versionId, version, status, synthesisTier, createdAt, active, canary); a version’s prompt, configuration, grants snapshot and hashes are never returned. See Versions and rollback and Tools.
  • GET /api/v2/agents/listConsumers and GET /api/v2/procedures/listConsumers list the published workflow version nodes that run the agent or procedure, with the exact version each pins. Drafts are never listed. The credential’s scopes must also include workflows:read, and a workflow the caller may not read at its home is left out (meta.partial: true when a home could not be decided). See Procedure consumers.
  • POST /api/v2/agents/reinstateVersion makes an exact prior version active again on an agent the calling External App owns, with agents:manage held at the agent’s home. It never attests the restored definition: the identity attestation lapses until a person attests the agent in the Console. Published workflow versions keep their pins.
  • Forge MCP adds forge_list_agent_versions, forge_list_agent_consumers, forge_list_tool_versions and forge_reinstate_agent_version in the agents group and forge_list_procedure_consumers in the workflows group (210 tools).
Retiring or reinstating skill, tool and procedure versions, and consumer reads for skills and tools, stay in the Console.
Machine credentials can read and maintain Blueprint roadmaps, workstreams and milestones, and read the critical path and blocked tasks.

Summary

GET /api/v2/roadmaps/list and get, GET /api/v2/workstreams/list and get, and GET /api/v2/milestones/list and get (scope objectives:read); POST /api/v2/roadmaps/create, PATCH /api/v2/roadmaps/update, POST /api/v2/workstreams/create, PATCH /api/v2/workstreams/update, POST /api/v2/milestones/create, PATCH /api/v2/milestones/update and POST /api/v2/milestones/rerank (scope projects:write, projects:manage); and GET /api/v2/planning/getCriticalPath and listBlockedTasks, with fifteen MCP tools in the projects group, read and maintain the Blueprint the way the Console does. See Roadmaps, Workstreams, Milestones and Planning projections.

New

  • Planning rows carry no home, so reads decide objectives:read and writes decide objectives:read and projects:manage at the deployment root; a refusal is 403 naming the first missing permission. Writes return what they wrote, so the credential’s scopes must include objectives:read as well as projects:write. Nothing is written on any refusal.
  • Lists page with cursors bound to their filters. Responses never include _creationTime or a milestone’s category override.
  • A milestone create needs an existing roadmap and workstream, every tagged objective must exist, and a rerank checks every id before ranking any (404 otherwise). A quarter move that would break a task dependency is 409 conflict with a fixed message naming only the quarter.
  • The critical path and blocked tasks also need the projects:read scope and include only ordinary tasks of projects the caller may read at their home, never factory tasks or an assignee; meta.partial reports a reached read bound or more than 50 projects decided.
  • A same-key retry within 24 hours returns the recorded result only while the caller still holds both permissions at the deployment root; otherwise 409 idempotency_result_unavailable.

Availability

Roadmaps, workstreams and milestones are never deleted over the API: archive with status ARCHIVED or CANCELLED. A milestone’s category, a person’s own blockers and the tasks they could help with stay in the Console.
Checked hosted MCP configurations for Claude Code and VS Code that sign in instead of using a key.

Summary

Where interactive sign-in is configured, Forge MCP generates Claude Code (.mcp.json) and VS Code (.vscode/mcp.json) configurations for the hosted endpoint that contain only its URL. The host signs you in with your Forge account and keeps the token; the sign-in starts with no access until it is given scopes and roles. See Sign in from a remote host.

New

  • credentialMode: "oauth" in buildHostedHostConfig (@tangogroup/forge-mcp), and the recovery results reauthenticate_in_host (401) and review_key_scopes_and_roles (403) from classifyCredentialRecovery.
  • Setup, re-authentication, revoke and recovery steps for both hosts, checked against the package builder.

Availability

Interactive sign-in stays off until a deployment’s operator configures it; until then use an MCP key. No live sign-in has been qualified yet, and nothing changes in the hosted endpoint, its credentials, permissions or scopes.
External Apps and platform API keys can see whether a workflow draft's Workflow Architect is waiting on a person.
GET /api/v2/workflows/getArchitectStatus and MCP forge_get_workflow_architect_status report whether a workflow’s draft has a live Workflow Architect conversation and whether a plan card or a synthesis batch waits on a person, under workflows:read at the workflow’s home. When one does, handoff links to the Console builder where a person decides. No plan text, conversation, synthesis item, cost or person id is returned; Architect conversations and their plan and synthesis decisions stay person operations in the Console.
Checked hosted MCP configurations for Claude Code and VS Code with a static MCP key.

Summary

Forge MCP now generates configurations for Claude Code (.mcp.json) and VS Code (.vscode/mcp.json) that reach the hosted endpoint at <console origin>/api/mcp with a static MCP key in the Authorization header. Claude Code reads the key from FORGE_MCP_KEY; VS Code prompts for it as a password input. The configurations never contain the key. See Connect a remote host.

New

  • Public buildHostedHostConfig and SUPPORTED_HOSTED_HOSTS in @tangogroup/forge-mcp.
  • Setup, rotation, revocation and recovery steps for the hosted key, checked with both configurations against the package builder.

Availability

Only an MCP key is supported for these configurations. External App tokens expire and the hosted endpoint cannot refresh them, so the builder refuses them; use the stdio server with client credentials. Interactive hosted OAuth sign-in remains unavailable, and nothing changes in the hosted endpoint, its credentials, permissions or scopes.
External Apps and platform API keys can read a workflow's published versions.
GET /api/v2/workflows/listVersions, getVersion and getVersionGraph, and MCP forge_list_workflow_versions, forge_get_workflow_version and forge_get_workflow_version_graph, page a workflow’s published versions newest first, read one, and read one version’s frozen nodes and edges in the draft graph shapes, under workflows:read at the workflow’s home. The publisher, output settings, default agents, vault and credential bindings are not returned. Rolling back, resetting the draft to a version and retiring a workflow stay person operations in the Console.