Claude Code v2.1.290 ·
Creating a cloud session now reports what was not applied
The cloud-session create command now prints the session ID, a notice and a not_applied list, and names the agent that requires a repository
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release
Unclear It is not clear what fills in the notice or the not-applied list.
What
The command that creates a cloud session (pool_headless) reports more about the result.
- It prints a notice and a
not_applied list of the parts of your request that the cloud session did not apply.
- The session ID is printed on its own, in a set format.
- The JSON output, the machine-readable form, adds
notice and not_applied. Before, it held only ok, session_id, title, url and pool_id.
- The create call passes
repositoryRequiredBy, which names the agent that needs a repository.
- Error reports can include
message_hidden. Errors are no longer handled by the old exit step.
- The create flow now tells the device bridge and served tools that a cloud client is involved (
cloudClient: true).
Nothing has been read about the gate tengu_remote_create_session_error.
Why
You can now see which parts of your request the cloud session did not apply. Scripts reading the JSON output gain two new fields to handle.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what fills in the notice or the not-applied list.
See this entry in the whole of v2.1.290 →
