macOS Apple Silicon
macOS 13 Ventura or newer
Download .dmgBring your own model: Claude, GPT, Gemini, any OpenAI-compatible API, or a local one. Houston reads, edits, searches, and runs code in your project, behind an approval flow you control.
An agent that edits files and runs commands needs hard limits, not just good intentions.
Shell commands run under Seatbelt on macOS and bubblewrap on Linux (when installed). Writes stay inside the project, and network stays off until you allow it, then only to domains on an allowlist. Where no sandbox exists, Houston says so and never auto-approves.
Plan mode, ask every time, auto-approve edits, or full auto. Edits show an inline diff before you approve, and your choices can become lasting rules. Reaching the network prompts the first time, even in full auto.
Each new chat in a git repo gets its own worktree and branch, so the agent never edits the files you are working in. Every turn's file changes revert in one click.
A repo can ship rules that only tighten, like always asking before touching infra/. Project config that would grant more is ignored until you trust the folder, and admins can lock a machine-wide policy.
Fetched pages are fenced off as untrusted content. A page that looks like a prompt injection is read by a separate model call with no tools and no history, and only its summary reaches the agent.
macOS builds are signed and notarized. Every release ships cosign-signed checksums, an SBOM, and SLSA build provenance, so you can check exactly what you installed and how it was built.
More than chat. It works in your repository with real tools, and you stay in the loop on every step that matters.
Claude (direct, Bedrock, Vertex AI, or Foundry), GPT, Gemini, any OpenAI-compatible endpoint, or a local model through Ollama or LM Studio. Switch per conversation.
Runs on your machine with no analytics or telemetry. Your code goes only to the model providers you configure.
Read, write, and patch files, run shell commands, inspect git, fetch and search the web, and work with pull requests. Reads run in parallel; writes stay in order.
Bundled ripgrep and ast-grep. Find calls, declarations, and JSX by syntax-tree shape instead of fragile regex. With a language server installed, it also jumps to definitions, finds references, renames across files, and catches errors its own edits introduce.
After starting your dev server it can screenshot the page and read the console, then fix what it finds. A live preview docks beside the chat.
Hand focused tasks to subagents with fresh context, and run a multi-agent review of your diff that checks correctness, security, and quality, then verifies its own findings.
Connect MCP servers over stdio, HTTP, or SSE, with OAuth sign-in for hosted ones. Define custom agents and skills in Markdown. Your project's own conventions are picked up too.
With the gh CLI signed in, it opens and reviews pull requests, reads and files issues, and checks CI status without leaving the chat.
Use the desktop app, an interactive terminal session, or one-shot headless runs for scripts and CI. A single-file CLI runs anywhere Node 22+ does, ACP-capable editors can run it as their agent, and a GitHub Action reviews pull requests and fixes failed CI on your own runners.
macOS 13 Ventura or newer
Download .dmgmacOS 13 Ventura or newer
Download .dmgWindows 10 or newer
Download .exeNot code-signed yet. If SmartScreen appears, choose More info, then Run anyway.
glibc 2.35+, e.g. Ubuntu 22.04
Download AppImageAlso as a .deb package.
Not sure which Mac you have? Open the Apple menu and choose About This Mac. If it lists a Chip (M1 or newer), get Apple Silicon. If it lists a Processor, get Intel.
On Linux for Arm? There is no desktop build for it yet, but the terminal CLI runs there with Node 22 or newer.
The same agent in your terminal, with no desktop app. Runs on macOS, Linux, and Windows, on x64 or Arm, with Node 22 or newer.
brew install houston-code/tap/houstonnpm install -g @houston-code/clibun add -g @houston-code/clicurl -fsSL https://houstoncode.ai/install.sh | sh Then start it with houston. Prefer a single file? Download houston-cli.cjs and run it with Node.
macOS builds are signed and notarized, Linux packages are GPG-signed, and every release has a signed SHA256SUMS. How to verify.
What changed in each version, plus every asset and past release, is on GitHub Releases.
Download for your platform and open Houston. There is no account and no sign-up.
In Settings, add an API key for at least one provider, or point Houston at a local model.
Pick a folder and an approval mode, then give it work. You review the actions that matter.
Something else? Open an issue or email dev@houstoncode.ai.
Houston is a cross-platform desktop coding agent. You point it at an AI model and a project folder, and it can read, edit, search, and run code, with every consequential action gated by an approval flow, and shell commands sandboxed where the operating system supports it.
Yes. Houston is free to download and run. You bring your own model API keys, or run a local model, and pay only whatever your chosen provider charges for usage. Houston itself adds no fee.
Claude (directly, or through Amazon Bedrock, Google Vertex AI, or Microsoft Foundry), GPT, Gemini, any OpenAI-compatible endpoint, and local models via Ollama or LM Studio. You can switch models per conversation, and the picker shows each model's context window and capabilities.
Houston runs on your device and collects no analytics or telemetry from the app. Your data leaves your machine only when you use a feature that reaches a provider you configured (sending a prompt, searching the web, or checking for updates), and only to that destination. The one usage signal we can see is the aggregate download and update-check count our download host keeps for released files, which holds no personal data and involves no in-app tracking.
macOS 13 Ventura or newer (Apple Silicon and Intel), Windows 10 or newer (x64), and Linux x64 (glibc 2.35+). A standalone terminal CLI also runs on macOS, Windows and Linux, x64 or Arm, with Node 22 or newer.
You choose an approval mode (from reviewing every action, to auto-approving edits, to full autonomy), and where the OS supports it, shell commands run in a best-effort sandbox. You stay in control of what executes.