Runtime client and ACP IDE connection
The Runtime client and ACP adapter use the same Core, conversations, agents and approvals as the normal interface. Connecting an IDE grants no server filesystem or terminal access and does not make it a trusted administrator. Use the original user’s valid connection, not a machine key carrying a human-looking identifier.
Prepare the connection
Select your Core origin, an existing workspace and an agent available to you. The software client first negotiates a supported protocol version. Resolve a version refusal by using compatible software, not by retrying with an invented capability.
The public Go client provides client.NewRuntime, Negotiate, CreateSession, Prompt and Observe. Save its ClientMessageID somewhere that survives a restart, before the first submission. After a timeout or restart, call Observe for the same conversation and message. This reads the original request rather than creating another generation. Do not reuse an identifier with different text.
Creating a conversation is a separate action. If its acknowledgement is lost, check the conversation list before creating another: automatic creation retries can add a second conversation.
Use ACP
The ACP adapter exchanges messages over standard input and output. Configure -core, -workspace, -agent, -cwd and a valid user token in AIHUMMER_RUNTIME_TOKEN. Keep the token out of shared projects and logs. The -cwd value labels the IDE project; it does not mount the computer’s directory on the server.
This adapter supports ACP1 and text input. It does not accept client-supplied MCP servers, new filesystem or terminal permissions, images or audio. Separate Core tools remain limited by their existing configured permissions.
Each conversation permits one active prompt. Two independent conversations can proceed independently. Loading a conversation shows persisted messages and original identities without resubmitting unfinished work.
Approval, cancellation and disconnects
Tool approval reaches the user with allow-once or reject choices. Missing, expired or malformed replies never mean consent. Core still validates the decision.
Explicit cancellation targets one active original input. Cancelling one conversation must not cancel another. Closing a connection does not itself establish cancellation; acknowledging a cancellation request does not prove that all in-progress operations have stopped. The client application distinguishes a final result, accepted background work and an uncertain external effect.
Partial output and transport EOF do not replace a persisted final result. Recover the original state when the outcome is unknown rather than sending the action again. External long-running operations have their own original-identifier readback.