The resolved shared-provider-dir’s CLAUDE.md path + content,
read-only. claude_dir is injected (not resolved internally) so this
is testable against a tempdir. content: None, exists: false for a
genuinely missing file (the common case — no AgentMux-spawned Claude
agent on this host has one today, confirmed 2026-08-24) — real I/O
errors (permission denied, etc.) still propagate as Err, not
silently folded into “missing.”
Restores name + instructions from target_version_id as a NEW
version (source: "revert", written_by: "armory-ui"), through the same
atomic upsert-plus-version primitive each tier’s ordinary save uses.
Loads a Global Memory entry for Memory → Global’s history commands: it must
exist, be is_global, and not be the blank singleton. System-tier rows
are allowed (see the comment above the registrations).
getagentbundles / setagentbundles: an agent’s Bundles list, the
bundles picked for it in order (Store::agent_bundle_ids). Its own bundle
isn’t in it: launch always puts that first. Window-scoped, like
setagentcontent: the new-agent form, the launch modal and the Stash call
these before the agent runs.
Memory → Global’s “Bring Global Memory from…” step for an isolated channel
(SPEC_MEMORY_FOLLOWS_THE_AGENT_2026_09_24.md §2.1.6). Registered with the
others below.
globalmemory:sections: the Global Memory block an agent’s startup file
carries, from the same store (id_store) and formatter the startup-file
writers use — so memory reinjection re-delivers it byte for byte,
Operator Config included (SPEC_GLOBAL_MEMORY_DELIVERY_2026_09_27.md §7 P1).
The directory a spawned Claude agent’s CLAUDE_CONFIG_DIR env var
points at by DEFAULT (agents not bound to an account — the common
case; an agent bound to an account uses that account’s own dir, which
this does not cover). Mirrors agent_open.rs’s own auth_dir
resolution exactly — DataPaths::provider_auth_dir("claude"), with the
identical ~/.agentmux/shared/providers/claude fallback when
DataPaths::from_env() fails — so the path shown here is genuinely the
one AgentMux itself uses when launching a Claude agent, not a guess.
codex P1, PR #2794: the original version read ~/.claude/CLAUDE.md
directly, which SPEC_PROVIDER_ISOLATION_2026_06_20.md
§5b confirms is NOT what a CLAUDE_CONFIG_DIR-redirected spawned agent
actually loads as its “user CLAUDE.md” — CLAUDE_CONFIG_DIR relocates
Claude Code’s entire home, <CLAUDE_CONFIG_DIR>/CLAUDE.md included.