stroblmeandClaude Opus 5
d01a8dad37
Follows the portal: the noun is "instance" everywhere the app says it — UI strings, CLI output, error details, docs and comments. The wire keys (`instance_id`, `instance_token`) and the hub route this calls move with it. An existing cloud.json is adopted rather than refused: without the key alias the dataclass fails to parse, which the caller swallows and reads as "never enrolled" instead of "reconnect". `instance_key` on a node type becomes `target_key`. It means the outside thing a node points at, which is a different sense of the word, and keeping both would put two meanings of "instance" in one codebase. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015YrQnKV3bnQd4K342y8tKj
8 lines
329 B
Python
8 lines
329 B
Python
"""The MCP endpoint: the same flow API, in the shape an agent can drive.
|
|
|
|
``server`` holds the tools, ``http`` wires them to the streamable-HTTP
|
|
transport and the OAuth resource-server checks. Both are imported lazily, only
|
|
when ``MCP_ENABLED`` is set, so an instance that does not want an agent
|
|
endpoint does not carry one.
|
|
"""
|