When your machine announces newer local changes and then drops off before uploading them, a new message tells the model the current turn is running on stale files and that the changes will arrive in a later turn. A second new warning tells you that dynamic workflows can burn through tokens by running subagents in parallel, pointing at /workflows and /config.
- The stale-files note is system-facing, meant to stop the model from acting as if it has the latest edits.
- The usage warning names
/workflowsand/configas where to look.
the changes arrive at a later turn once the machine is back.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
With `disableEssentialTelemetry`, `disableNonessentialTelemetry`, `disableNonessentialServices`, and `disableAutoUpdates` all set to `true`, the desktop application makes **no outbound connections to Anthropic-operated hosts at runtime**. …third-party/claude-desktop/telemetry see the edit
* [Workflows are turned off](/docs/en/workflows#turn-workflows-off)model-config see the edit
`effortLevel` accepts an [effort level](/docs/en/model-config#adjust-effort-level) name. It also accepts `"ultracode"`, which requests `xhigh` effort with [ultracode](/docs/en/workflows#let-claude-decide-with-ultracode) on. `applyFlagSetti…agent-sdk/typescript see the edit
| `.mcp.json` | MCP servers bundled with this plugin. A JSON object keyed by server name: `{"mcpServers": {"<name>": {"type": "http", "url": "...", "oauth": true}}}`. A remote entry uses `type` (`http` or `sse`), not `transport`, and suppo…third-party/claude-desktop/extensions see the edit
Anthropic's documentation has since written up /config, on MCP, plugins, skills, and hooks.