# Threadlines

Threadlines, the open-source ADE for Claude Code, Codex and other coding agents

[![CI](https://github.com/Threadlines/threadlines/actions/workflows/ci.yml/badge.svg)](https://github.com/Threadlines/threadlines/actions/workflows/ci.yml) [![Latest release](https://img.shields.io/github/v/release/Threadlines/threadlines)](https://github.com/Threadlines/threadlines/releases/latest) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE) [![As seen on Open Source Alternatives](https://www.opensourcealternatives.to/badge-osa.svg)](https://www.opensourcealternatives.to) **[Website](https://www.threadlines.dev/?ref=readme) · [Download](https://www.threadlines.dev/download?ref=readme) · [Supported agents](https://www.threadlines.dev/agents?ref=readme) · [Changelog](https://www.threadlines.dev/changelog?ref=readme) · [Latest release](https://github.com/Threadlines/threadlines/releases/latest)** Threadlines is an open-source ADE (agentic development environment) for Claude Code, Codex, OpenCode, Cursor, and other coding agents. Keep the agent conversation, a live browser, project files, terminal, and source control open together so you can see, steer, and recover agent work without reconstructing context across tools. ## Why Threadlines - **All your computers in one app.** Link your Mac, a Windows PC, a Mac mini or a Linux box. An agent on one can start a thread on another when it needs that machine, after asking you first unless you allow it, and Fleet shows what every computer is running. - **Several agents in one thread.** Add a second agent to check the first one's work, or ask Codex or Claude a question while another agent keeps going. - **Agents start their own threads.** An agent can split a big job across new threads, each on the model it picks, and their answers come back to it. - **Agents in your terminal can use it too.** Once you approve them, Claude Code, Codex, Gemini CLI or Cursor can start threads here and follow them. Scripts can do the same with the `threadlines` command. - **Scheduled and event tasks.** An agent starts on your prompt at the times you pick, or when a GitHub issue gets a label or a webhook comes in, while Threadlines is running on that computer. - **Pull requests and CI beside the chat.** Review a pull request and its checks next to the thread that made it, and send feedback straight to the agent. - **A browser beside every thread.** Review visual changes and send the exact page state back to the agent without leaving the workspace. - **Source control you can act on.** Inspect per-file changes and the commit graph, then commit, push, and open a pull request from the same app. - **Exact context instead of repeated prompts.** Attach selected reply, code, or terminal lines directly to the next message. - **Nothing runs invisibly.** Track tasks, subagents, and background processes, including their live state and stop controls. - **Durable sessions, any agent.** Resume work after restarts and switch a thread to another agent without losing the conversation or working tree. - **Set up in minutes.** A first-run checklist installs the agent CLIs with one click and signs you in without leaving the app. - **Your phone is a client.** Pair it with a QR code and check on running threads from anywhere, against the desktop app or a self-hosted server. It alerts you when an agent needs you, finishes or fails, and a swipe pins a thread or wraps it up. - **One usage picture across machines.** Token and cost dashboards read the agents' own transcripts on every computer you run, merged into one view. ## Screenshots | See every computer | Every project in one sidebar | Pick your agents | | ----------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | ![Fleet: a MacBook Pro and a Windows PC, the agents at work on each, and their threads](apps/marketing/public/Screenshots/app/fleet.webp) | ![The sidebar with threads from four projects, one running on a Windows PC under the thread that started it](apps/marketing/public/Screenshots/app/sidebar.webp) | ![Threadlines setup asking which agents you use, with nine agents to pick from](apps/marketing/public/Screenshots/app/onboarding.webp) | ## Installation > [!NOTE] > Threadlines drives coding agents installed on your computer, such as > [Codex](https://developers.openai.com/codex/cli) and > [Claude Code](https://claude.com/product/claude-code) (see > [Supported agents](#supported-agents)). If one is missing, the first-run setup > installs it with one click and signs you in without leaving the app. > Installing them yourself beforehand works too. ### Desktop app Install the latest stable desktop app from the [download page](https://www.threadlines.dev/download?ref=readme) or [GitHub Releases](https://github.com/Threadlines/threadlines/releases/latest). Signed Windows and macOS builds and a Linux x64 AppImage are published through the desktop release workflow. Linux builds are unsigned; integrity for auto-updates is verified through the updater manifest hashes. Then open a local project and start a thread with the agent you already use. ### Self-host with Docker Run Threadlines on a VPS or home server and connect from any browser or your phone: ```bash docker run -d --name threadlines --restart unless-stopped \ -p 3773:3773 \ -v threadlines-home:/home/threadlines \ -v /path/to/your/repos:/workspace \ ghcr.io/threadlines/threadlines:latest ``` See [docker/README.md](./docker/README.md) for the full guide, including phone pairing and safe remote access. ### Server CLI The npm package supports advanced CLI/server and remote-bootstrap usage: ```bash npx @threadlines/server@latest --help ``` > [!IMPORTANT] > The server requires **Node.js 22.22.2+, 24.15+, or 26+**. Odd-numbered Node > releases are not supported. ### Local development ```bash vp install --frozen-lockfile vp run dev ``` On Windows, clone the repository **outside** OneDrive-synced folders (Desktop/Documents by default). Syncing `node_modules`, `.git`, and build output noticeably slows installs, builds, and file watching. ### Local desktop artifact ```powershell vp install --frozen-lockfile vp run dist:desktop:artifact -- --platform win --target nsis --arch x64 --build-version 0.3.0 ``` The artifact is written to `release/`. ## Supported agents Threadlines runs these coding agents, signed in with your own accounts: - [Codex](https://www.threadlines.dev/agents/codex?ref=readme) by OpenAI - [Claude Code](https://www.threadlines.dev/agents/claude-code?ref=readme) by Anthropic - [OpenCode](https://www.threadlines.dev/agents/opencode?ref=readme) by Anomaly - [Cursor](https://www.threadlines.dev/agents/cursor?ref=readme), through the Cursor CLI - [Antigravity](https://www.threadlines.dev/agents/antigravity?ref=readme) by Google - [Grok Build](https://www.threadlines.dev/agents/grok?ref=readme) by xAI - [fx](https://www.threadlines.dev/agents/fx?ref=readme) by Vercel - [Muse Code](https://www.threadlines.dev/agents/muse-code?ref=readme) by Meta - [Pi](https://www.threadlines.dev/agents/pi?ref=readme) by Earendil Other agents from the open [ACP registry](https://github.com/agentclientprotocol/registry) can run as community agents. Threadlines installs them but hasn't tested them. See [docs/providers/community-agents.md](./docs/providers/community-agents.md). ## Origins Threadlines began as a fork of [T3 Code](https://github.com/pingdotgg/t3code) and has since grown its own product direction, branding, release pipeline, provider orchestration, and source-control workflow. Upstream remains a source of inspiration, and improvements flow back when they fit. The upstream Git history and MIT attribution are kept intact. See [docs/fork-separation.md](./docs/fork-separation.md) for the origins and compatibility policy. ## Configuration - Configure Threadlines with `THREADLINES_*` environment variables. - New installs keep their data in a separate `~/.threadlines` directory. - The `threadlines` CLI is the supported command. Usage analytics are enabled by default in official builds and can be disabled from Settings. See [docs/telemetry.md](./docs/telemetry.md) for what Threadlines collects and what it deliberately does not collect. ## Releases Threadlines keeps the upstream Git history but uses its own app versions starting at `0.0.1`. See [docs/release.md](./docs/release.md) for the desktop release workflow, platform status, signing requirements, and auto-update behavior. ## Development Notes Do not commit `.env` files, tokens, private keys, local app data, customer data, or screenshots containing secrets. See [SECURITY_GUARDRAILS.md](./SECURITY_GUARDRAILS.md) before publishing code or release artifacts. Before local development, prepare the environment and install dependencies: ```bash # Optional: only needed if you use mise for dev tool management. mise install vp install ``` Help is welcome, from bug reports to new features. See [CONTRIBUTING.md](./CONTRIBUTING.md) for setup and how review works. ## Support development Threadlines is free and open source. Optional sponsorships help cover ongoing development and operating costs such as domains, code signing, CI, and hosted Phone Link infrastructure. See [SUPPORT.md](./SUPPORT.md) for the no-perks sponsorship policy and support channels.