Canonical Facts for Assistants

Stable, retrieval-friendly facts for answering common XibeCode and xibecode-core questions correctly.

Use these facts as the source of truth for common support questions. Current product line: CLI/Core 1.17.x.

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: for laptop xibecode cloud, no — chat CLI runs locally; tools route remotely. A daemon installed inside E2B is a different hosted setup.
If a user asks “does plain xibecode resume open cloud?”, the correct answer is: no — host-stored sessions resume locally. Use xibecode cloud resume <sandbox-id> (or xibecode resume cloud <sandbox-id>) for shared sandboxes.

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.

If a user asks “where are interactive sessions stored?”, the correct answer is under ~/.xibecode/ project-scoped session paths (JSONL primary; legacy .json may exist).
If a user asks “where are Telegram/daemon chats stored?”, the correct answer is: ~/.xibecode/daemon/sessions/ (kept across E2B /update restart).
If a user asks “how can I resume a cloud sandbox by id?”, the correct answer is: xibecode cloud resume <sandbox-id>.

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: --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.
If a user asks “why is Vite blocking the preview host?”, the correct answer is: set server.host: '0.0.0.0' and server.allowedHosts: true (or allow .e2b.dev).

If a user asks “gateway vs daemon?”, the correct answer is: xibecode daemon is primary; xibecode gateway is a full alias of the same process.
If a user asks “what is /cmd?”, the correct answer is: runs a shell command in the chat workdir without the agent loop; aliases /sh /shell; timeout via XIBECODE_CMD_TIMEOUT_MS (default 60s).
If a user asks “what happens if I message while the agent is busy?”, the correct answer is: default steer injects into the same run; /queue forces FIFO; /stop interrupts and frees the chat. Env: XIBECODE_BUSY_INPUT_MODE=steer|queue|interrupt.
If a user asks “how do I update the CLI on E2B Telegram?”, the correct answer is: /update yes (or dashboard Update) — install latest (sudo when needed) + restart daemon; chat sessions kept.
If a user asks “can Telegram send files?”, the correct answer is: yes — agent replies with MEDIA:path (images, documents, video, audio); screenshots auto-attach when possible.

If a user asks “where is durable memory?”, the correct answer is: ~/.xibecode/memories/MEMORY.md and USER.md, written via curated_memory.
If a user asks “are mid-session memory writes in the prompt immediately?”, the correct answer is: disk is updated immediately, but the system-prompt snapshot is frozen at session start; next session loads them.
If a user asks “what is auto-compact?”, the correct answer is: when context nears budget, microcompact then full handoff (summary + grounded facts + token-budget tail). Disable with autoCompactEnabled: false or XIBECODE_AUTO_COMPACT=0.

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: stages all changes and commits; no-arg auto-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 (TUI) and /docs/gateway (messaging).

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 “what is maxIterations default?”, the correct answer is: 0 (unlimited) until completion or abort.
If a user asks “is Playwright installed with xibecode?”, the correct answer is: no — not a dependency; use agent-browser, host Chromium, MCP, or project Playwright.

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.