Founding Bot X guides
How to install, set up, and use Founding Bot X.
Founding Bot X can run installed ACP commands or coding agents from the official ACP Registry. Registry agents bring their own models, tools, and sign-in, while Founding Bot X provides projects, threads, checkpoints, and task delegation.
On web and desktop, consecutive tool calls appear as an expandable summary. Open it to inspect commands, tool inputs, status, and exit codes. Expand a tool call to see its output. A running command's output updates live, and long output shows only its most recent part. Use Open diff on a file change to review its contents.
Founding Bot X runs Google's official Antigravity ACP agent on your selected environment. It has its own sign-in, separate from the Antigravity IDE or CLI. Google controls which models and account access are available through this agent.
On web and desktop, open Settings → Appearance to choose a theme and follow the system appearance or stay in light or dark mode. To use different themes for light and dark mode, select the corresponding preview within each theme. Appearance preferences are saved separately on each device or browser.
Founding Bot X uses Claude Code's login and configuration. Start with the default provider for one account; provider setup covers installation and shared provider settings.
Use your ChatGPT plan or an existing Codex CLI login to code in Founding Bot X.
Founding Bot X transfers conversation context when you switch providers, continue through a portable restart, or use a fork that the provider cannot resume itself.
Cursor V2 runs through the official @cursor/sdk TypeScript package. It does not use Cursor's ACP transport for V2 execution.
The Device panel shows a live iOS Simulator or Android Emulator next to a thread, so you can watch an agent verify mobile work and tap the device yourself. Agents get the same device through device_* tools and the agent-device command line, which Founding Bot X sets up for them.
When an agent asks a question that accepts a custom answer, use Attach files or paste an image into the answer field. On mobile, use the attachment button to choose photos or files. You can send a file by itself, with a selected option, or with a typed answer.
Founding Bot Connect troubleshooting
A Founding Bot Connect connection goes through four parts, in this order:
The desktop app can import cookies from another browser so you can reuse its signed-in sessions in the preview browser.
Founding Bot X runs coding agents on your computer and lets you control them from its desktop, web, or mobile app. Set up the machine where the agents will work first.
Customize shortcuts in Settings → Keybindings on web and desktop. That page also lists the command IDs and defaults available in your version.
The command palette keeps focus while open. Closing it returns focus to the composer. While the palette or model picker is open, number shortcuts select its entries instead of switching threads. Model shortcuts work in Settings as well as the composer. See Keybindings to customize these shortcuts.
Give the agent a task in the composer. Add files, quote a previous response, or include a skill when the task needs more context.
Sign in to Founding Bot Connect, link your environments, and enable Device Notifications in Settings → Notifications to receive alerts when an agent finishes, fails, needs approval, or asks for input. Tap a notification to open its thread. Your environment must have agent activity publishing enabled.
Muse Code is a beta integration and is disabled by default. Install Muse Code on the machine hosting your environment, then run muse login as the account that runs Founding Bot X.
Founding Bot X includes third-party software and adapted assets. To read their license and attribution notices:
Install and authenticate OpenCode on the machine running your environment, then enable it in Settings > Providers. See provider setup. Founding Bot X requires OpenCode 1.14.19 or newer, including when you connect an existing OpenCode server.
Agents that Founding Bot X did not start can work with an environment through its MCP server. They can read projects and threads, start and message threads, and check which providers and models are available. This covers Claude Code or Codex in your own terminal, ChatGPT, and bots that support MCP. Each agent signs in once, and you choose what it may do.
Permission modes control when an agent needs your approval to act. Choose a mode in the message composer; it applies to that thread.
Founding Bot X can use your existing Pi coding agent installation while keeping Pi's models, auth, extensions, skills, context files, and native session history.
The server does not send product usage data unless you turn it on. With FOUNDINGBOT_X_TELEMETRY_ENABLED=true and a PostHog project key in FOUNDINGBOT_X_POSTHOG_KEY (and optionally FOUNDINGBOT_X_POSTHOG_HOST), the server sends product usage events to that PostHog project, associated with a hashed account or installation identifier. To count how many installations one person uses, it also sends hashed account identifiers: your Founding Bot account, your OpenAI and Claude accounts when you are signed in, and a random identifier for each device that connects. Events include the provider, model, reasoning effort, permission mode, turn result, duration, release channel, and main-agent token totals when available.
A prompt link opens Founding Bot X with a prompt ready to send. Use one to share a prompt on social media, or to put a one-click fix in a pull request comment.
Connect a phone, browser, or another desktop app to Founding Bot X running on a different machine. That machine must stay running and reachable while you work.
Running Founding Bot X in the background
On Linux and macOS, Founding Bot X can run as a service for your user so you do not need to keep a terminal open.
Settings and project overrides
On web and desktop, the "Applying settings for …" sentence at the top of Settings pages picks the project and environment a change applies to. Pages that only hold device preferences, such as Appearance, don't show it. They start at All projects and All environments and stay selected as you move between categories or search for a setting.
A SnapShot captures the window you are working in and attaches it to your current draft. The attachment carries the app name and window title, and when available the app icon and the window's accessibility data (its controls, text, and their positions in the image). Agents can use that data to reason about the screenshot.
Founding Bot X integrates with GitHub, GitLab, Forgejo, Gitea, Bitbucket, Azure DevOps, and GitCafe to clone and publish repositories, create pull requests, and review changes.
Each terminal keeps up to 5,000 lines and 8 MiB of scrollback on its environment server. Founding Bot X removes the oldest output when either limit is reached. A long line can be shortened at the start. New terminal output is not truncated.
The app you use and the server running your agents can be on different machines. When a server is behind your web or desktop app, an update notice appears in the conversation and Settings → Connections. Update the machine named in that notice.
Open Usage from the sidebar or the command palette, or press mod+u on web and desktop when the terminal is not focused. Customize usage.open in Settings → Keybindings.
Use Founding Bot X as your default browser
On macOS, the desktop app can be your default web browser. Links you open from other apps then open in Founding Bot X. When the thread on screen shows its browser panel, the link opens there as a new tab. Otherwise it starts a new thread without a project, with the browser panel maximized on the page, so you can ask an agent about it right away.
Agents can answer with a page instead of only text: a chart, table, diagram, image collage, or mockup. Ask for one ("show this as a chart", "make a collage of these screenshots") and the agent builds a self-contained HTML page, which appears in the thread above its written reply. It works with every provider, on web, desktop, and mobile.
Founding Bot X shows a setup flow when you open a new installation. Existing workspaces skip this flow.
Use a new thread for a separate task. Choose New worktree when its code changes need a separate branch and working directory.