Atlas session sharing fails with Sharing is disabled in configuration because SessionShare.share reads config and throws when `share` is set to "disabled". A related failure is No active account token available for sharing, because the share backend requires an active account token. The fix is to remove `"share": "disabled"` from your Atlas config, or set it to the mode you want, and run `atlas login` so an account token exists before sharing.
Why does Atlas say Sharing is disabled in configuration
Atlas says Sharing is disabled in configuration because SessionShare.share reads config and throws when `share` is set to "disabled". The check runs before any network call in the 2026 build, so a disabled config fails immediately and no session data leaves the machine.
Sharing is disabled in configuration is a configuration verdict, not a service outage. SessionShare.share looks at the `share` key, sees "disabled", and refuses. Nothing is uploaded and no URL is minted. Two different failures live in this area and they are worth separating. Sharing is disabled in configuration comes from the config check. No active account token available for sharing comes later, from the share backend, which requires an active account token and throws when there is none. Reading which message you got tells you which of the two fixes you need.
How to enable session sharing in Atlas
Enable Atlas session sharing by removing `"share": "disabled"` from your Atlas config, or by setting it to the mode you want. SessionShare.share reads that 1 key on every share attempt, so the change takes effect on the next share once the config is saved.
Edit the Atlas config and take out the disabled setting, or replace it with the sharing mode you actually intend. Keep in mind why it may have been set: an organization that turned sharing off did so on purpose, and quietly flipping the key on a work machine may violate a policy you did not write. If the setting is yours and you want sharing back, remove it. If the setting belongs to your organization, treat the local transcript export as the supported path instead of overriding the config.
How to fix No active account token available for sharing in Atlas
Fix No active account token available for sharing in Atlas by running `atlas login` so an account token exists before you share. Sharing clears 2 checks, not 1: the config must permit it, and the share backend still requires an active account token, and it throws when there is none.
The two conditions are independent, and both must hold. Config that allows sharing plus no signed-in account produces No active account token available for sharing. A signed-in account plus `"share": "disabled"` produces Sharing is disabled in configuration. Run `atlas login` to establish the token, then retry the share command. If the login succeeds and sharing still reports no active account token, the token is not being picked up by the process that is running Atlas, which usually means the login happened under a different user or a different home directory than the one Atlas is reading.
How to verify Atlas session sharing works
Verify Atlas sharing by retrying the share command once the config and the account token are both in place. A share that returns a URL, instead of Sharing is disabled in configuration or No active account token available for sharing, confirms SessionShare.share cleared both of its 2 checks.
Check the two preconditions in order before retrying. First, confirm `"share": "disabled"` is gone from the Atlas config, since SessionShare.share reads config and throws on that value before doing anything else. Second, confirm `atlas login` has produced an active account token, since the share backend requires one. With both satisfied, the share command completes and hands back a URL. If either error reappears, the message names which precondition is still missing, so you never have to guess which half failed.
How to fix it
- 01Remove `"share": "disabled"` from your Atlas config, or set it to the mode you want.
- 02Run `atlas login` so an account token exists before sharing.
- 03If your org disables sharing deliberately, export the transcript locally instead of sharing a URL.
- 04Retry the share command once both the config and the account token are in place.
Frequently asked questions
- how to fix Sharing is disabled in configuration in Atlas
- Remove `"share": "disabled"` from your Atlas config, or set it to the mode you want. SessionShare.share reads config and throws whenever `share` is set to "disabled".
- what does No active account token available for sharing mean in Atlas
- The Atlas share backend requires an active account token and throws when there is none. Run `atlas login` so an account token exists, then retry the share command.
- why does Atlas sharing fail even after I signed in
- Config and account token are separate preconditions. If `share` is still set to "disabled" in your Atlas config, SessionShare.share throws Sharing is disabled in configuration regardless of your login state.
- how do I share an Atlas session when my company blocks sharing
- Export the transcript locally instead of sharing a URL. If your org disables sharing deliberately, the config setting is intentional and the local export is the supported path.
- where is the Atlas share setting configured
- In your Atlas config, under the `share` key. Setting it to "disabled" makes SessionShare.share throw Sharing is disabled in configuration on every attempt.
- does Atlas upload my session before the sharing check runs
- No. SessionShare.share reads config and throws when `share` is set to "disabled", so a disabled configuration fails before any session data is sent.
Try Atlas in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install AtlasRelated guides
Atlas with Poolside Laguna M.1 in 2026
Poolside Laguna M.1 in Atlas, 2026: a coding-native reasoning model with 262,144 tokens of context, free on Poolside's API and $0.20/$0.40 per Mtok on OpenRouter.
Atlas with Magistral Medium: Multi-Hop Root-Cause Debugging in 2026
Magistral Medium reasons across a 128,000 token window at $2.00 / 1M input tokens and $5.00 / 1M output tokens. Atlas setup, the 16,384 token output cap, tradeoffs.
Atlas with GPT-OSS 120B (local via Ollama): Offline Reasoning for Air-Gapped Work in 2026
GPT-OSS 120B is the strongest fully offline reasoning model for Atlas: a 65GB MXFP4 download, 131,072 token context, free self-hosted, or $0.15 / $0.60 per Mtok on Groq.
Atlas with Ministral 8B: The Cheap Slot That Can Still Call Tools in 2026
Ministral 8B runs 128,000 tokens at $0.10 / 1M input tokens and $0.10 / 1M output tokens, symmetric. The Atlas small_model upgrade when subagents misfire on schemas.
Atlas with Qwen2.5-Coder 7B (local via Ollama): the Laptop Setup in 2026
Qwen2.5-Coder 7B runs Atlas on a laptop with no discrete GPU: about 5GB at 4-bit, a 32,768 token context, and free self-hosted. Setup, limits, and when to upgrade.
Atlas with Ministral 3B: The $0.04 Housekeeping Model in 2026
Ministral 3B is the cheapest model Mistral sells: $0.04 / 1M input tokens and $0.04 / 1M output tokens across 128,000 tokens. Atlas small_model setup and limits.
Atlas for Blazor: Terminal-Native AI Coding for .razor Components in 2026
Atlas is a terminal-native AI coding agent for Blazor developers in 2026. Work across .razor components, render modes, and the C# and JS interop boundary safely.
Atlas with Claude Sonnet 5: The 2026 Everyday Driver
Claude Sonnet 5 gives Atlas a 1M token window at $2 / $10 per Mtok, 60 percent under Opus 4.8 input pricing. Why it is the default for long agentic sessions in 2026.