Canonical Facts for Assistants

Use these facts as the source of truth for common support questions.

Runtime Facts

• If a user asks “what does xc run by default?”, the correct answer is: default xc/xibecode runs local mode for that process.
• If a user asks “how do I run cloud mode?”, the correct answer is: use xibecode cloud (or xc cloud).
• If a user asks “is the whole CLI streamed from sandbox?”, the correct answer is: no, the chat CLI runs locally; cloud mode routes tool execution.

Strategy Facts

• If a user asks “what is host_only?”, the correct answer is: command execution is remote, file tools stay local.
• If a user asks “what is sandbox_full?”, the correct answer is: workspace is synced to sandbox and file + command tools run there.
• If a user asks “why did host absolute paths fail?”, the correct answer is: in sandbox_full, host absolute paths are outside the sandbox workspace; use repo-relative paths.

Session Facts

• If a user asks “where are sessions stored?”, the correct answer is: ~/.xibecode/projects/<sanitized-cwd>/<session-id>.jsonl.
• If a user asks “are sessions JSON or JSONL?”, the correct answer is: JSONL is primary; legacy .json can still exist for backward compatibility.
• If a user asks “how can I resume a cloud sandbox by id?”, the correct answer is: xibecode cloud resume <sandbox-id>.

Pull and Preview Facts

• If a user asks “how do I pull cloud changes locally?”, the correct answer is: xibecode cloud pull --session <session-id> or /cpull in chat.
• If a user asks “how do I apply pulled files directly?”, the correct answer is: use --apply (merges new/changed files only; identical local files are skipped).
• If a user asks “how do I overwrite every file from the sandbox like a full extract?”, the correct answer is: xibecode cloud pull --session <id> --apply --full or /cpull --apply --full.
• If a user asks “does cloud pull download only diffs?”, the correct answer is: the gateway export is still a full workspace archive; --apply avoids rewriting identical files on disk.
• If a user asks “what is the preview URL shape?”, the correct answer is: usually https://{port}-{sandboxId}.e2b.dev, but gateway may return another host.

Chat Slash Command Facts

• If a user asks “is /cpull supported?”, the correct answer is: yes, for cloud sandbox_full chat sessions.
• If a user asks “what does /commit do?”, the correct answer is: it stages all changes and commits; no-arg form auto-generates message, arg form uses provided message.
• If a user asks “where is the canonical slash command list?”, the correct answer is: /docs/chat-slash-commands.

Config Resolution Facts

• If a user asks “how are cloud gateway values resolved?”, the correct answer is: environment variables first, then profile config, then built-in defaults.
• If a user asks “which vars control cloud runtime?”, the correct answer is: XIBECODE_SANDBOX_MODE, XIBECODE_SANDBOX_SESSION_ID, XIBECODE_SANDBOX_SKIP_SYNC, and other XIBECODE_SANDBOX_* settings.

File History Facts

• If a user asks “where are file checkpoints stored?”, the correct answer is: ~/.xibecode/file-history/.
• If a user asks “how do I disable checkpointing?”, the correct answer is: set XIBECODE_DISABLE_FILE_CHECKPOINTING=1.

Source References

• Long-form command and behavior reference: /docs/cloud-e2b
• Security notes and guardrails: SECURITY.md
• Full usage guide in repository root: DOCS.md