401 unauthorized from /api/v2 and /api/v3 now carries the header
WWW-Authenticate: Bearer, as RFC 6750 and RFC 9110 require, so an HTTP client can tell which
scheme to authenticate with. The status, the error envelope
and its messages are unchanged./forge/console routes. The authoring guidance describes how to keep instructions factual and verified against the product.GET /api/v2/tools/list and GET /api/v2/memory/list (the channel and longterm layers)
could answer the last page with hasMore: false and a non-null nextCursor. They now answer
nextCursor: null whenever hasMore is false, as every other
paged list does. Stop when hasMore is false./api/ path does not take now answers 405 instead of 404,
in the same not_found error envelope with the same Allow
header naming the methods that path takes. This holds for /api/v2 and /api/v3. A path no
method serves still answers 404.A request that sends no Authorization: Bearer <key> header now answers 401 unauthorized with
the message No API key was sent: send it as Authorization: Bearer <key>. A key Forge cannot accept
still answers Invalid or expired API key. The status and code are unchanged.forge_ask_workflow_architect, listed by default and by therunjob, asks the Workflow Architect to build a workflow or change one, so its authoring skill and the draft’s conversation apply instead of direct node and edge edits. It follows the Architect’s turn up tomaxWaitSecondsand returns the reply, the nodes and edges the turn added, changed or removed, and any plan waiting on a person, with a continuation while the turn runs. Personal key only. See MCP Server.
- Every listed MCP tool has a
title, a short display name such asList Runs, for a client to show in place of the tool’s name. - Each description’s example call uses an id in the form a real id has: a run id is a Convex document id such as
jn7s143a6994bazdfb2t6ta1918hk52p, and an org unit id readsorgunit_…. Examples no longer show placeholder ids such asworkflowRuns:abc123, which no Forge id has. Tool names and input and output schemas are unchanged.
/api/ path does not take answers 405 with the new error code
method_not_allowed, and its error.docUrl points at
that code’s section. It still carries the Allow header naming the methods the path takes. Before
this change the same 405 carried not_found. A path no method serves still answers
404 not_found. This holds for /api/v2 and /api/v3.x-forge-permissions in the OpenAPI document. Before, the array was empty and the key appeared only
in the description. This covers 61 operations: the admin operations whose grant is decided at the
record’s home (for example POST /api/v2/chat/admin/archive, chat:manage), your own Personal key
operations under /api/v2/api-keys/admin/own-keys, the human-task writes
(approvals:approve), the human-task requests (human_tasks:use) and
GET /api/v2/capabilities/getBindingReadiness (credentials:read). Your credential’s scopes must
reach that key. Each key is a catalog permission. Operations that
only read your own records, such as GET /api/v2/actor and GET /api/v2/me, still list none.
Descriptions, operation ids and request and response shapes are unchanged.approvals:approve for the human task actions. Their descriptions began “Requires no permission:”, while their x-forge-permissions already named that key. They now begin “Requires the credential’s scopes to reach <key>.” and then say what else decides. An operation that reads no key at all still begins “Requires no permission:”. Only the wording changes: no x-forge-permissions value and no behavior changes. See conventions.POST /api/v2/skills/create or PATCH /api/v2/skills/update now
answers 500 internal_error with the message Unexpected error and the request id in
meta.requestId and the X-Request-Id header, as other routes do. Before, the message was the
internal error’s own text. Quote the request id when you report the failure. A duplicate skill
still answers 409 conflict and a skill that is not editable still answers 422, each with its
own message. See errors.- The MCP server instructions tell a connection that lists
forge_ask_workflow_architectto build or change a workflow by asking it, and to edit draft nodes and edges directly only for a precise edit it already knows. - The instructions’ read sentence now says
forge_call_read_operationruns aGEToperation or a knowledge read. - The six draft node and edge write operations,
createWorkflowDraftNodethroughdeleteWorkflowDraftEdge, open their descriptions with the same route: ask the Workflow Architect (sendWorkflowArchitectMessage) to build or change a workflow, and use the operation for a precise edit. Their inputs, outputs and permissions are unchanged.

