All stories
Nuphos Ecosystem Community reports

Nuphos wants Claude and Codex questions to stop disappearing

New CLI and runtime releases route native coding-agent questions into a shared Inbox, with a device-mode packaging exception users should check before updating.

Sources (4)

Why now Nuphos published CLI 0.8.3 and Runtime 0.1.41 on October 29, documenting a concrete repair to how Claude Code and Codex request human input.

Nuphos is tackling a small failure with large consequences for shared coding-agent sessions: an agent asks a question, but the person never receives it. Its October 29 CLI 0.8.3 and Runtime 0.1.41 releases describe forwarding native Claude Code and Codex questions into the workspace’s Inbox and pending-input interface.

The project says Claude Code’s AskUserQuestion was disallowed because its runtime client did not advertise form elicitation. Codex’s request_user_input, meanwhile, received empty answers immediately. The new adapters register those questions through Nuphos’s request_user_decision mechanism and tell the agent to end its turn until the person replies.

The answer comes back as a message

This is an integration change in a shared agent workspace, rather than a new model or an official change to either provider’s product. Nuphos wraps coding agents behind Agent Client Protocol adapters and lets teams continue sessions across local, remote and managed machines.

The answer arrives as the next user message, not as the original tool result. Multiple questions become one numbered request with choices inline. The native tool card can appear denied beside the decision card, so that visual state does not by itself mean the question failed to register.

The public implementation discussion also records handling for Codex questions marked isSecret: those requests fail rather than being forwarded as ordinary chat questions. That is a specific implementation safeguard described by the maintainers, not an independent security assessment.

Check which runtime you actually run

The important exception is in the published runtime image. Runtime 0.1.41 still bundles the CLI 0.8.2 agent host. Containers started in device mode with NUPHOS_JOIN_TOKEN use that older host and therefore do not receive the new question bridge through this image alone. Containers outside device mode use a different execution path. CLI 0.8.3 contains the agent changes; Desktop 0.96.0 carries the local-runtime changes and lists open questions beside chat.

Existing CLI users can run nuphos update, then restart a running nuphos agent; the agent requires Node.js 22 or later. Managed-runtime updates require an administrator and restart the runtime, potentially interrupting a turn. Publishing images does not update existing deployments automatically.

The same CLI release adds waking a paused Box during sign-in, requiring backend 0.106.0. Reporting the cause of an agent’s death between turns also requires that backend version. These compatibility requirements are separate from the native-question forwarding.

Nuphos says users keep their existing coding-plan subscription without an extra model charge from this arrangement; that is not a statement that managed infrastructure is free. Connected integrations give the agent access to the accounts behind the workspace panes, so existing account permissions still matter.

The release explicitly says a live Claude Code or Codex turn in a built runtime image had not yet been verified. The useful news is the documented repair and its installation boundaries; successful end-to-end behavior remains a maintainer claim rather than an AITrending test result.