cd /news/ai-agents/show-hn-tarobird-an-open-source-im-f… · home › topics › ai-agents › article
[ARTICLE · art-171826] src=github.com ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Show HN: TaroBird – An Open-Source IM for Codex, Claude Code and Other CLIs

TaroBird, an open-source self-hosted workspace from developer cloveric, launched on GitHub with iOS App Store and TestFlight builds to bring command-line AI agents including Codex, Claude Code, Kimi Code, DeepSeek Harness and Antigravity into a single conversation interface. The tool runs the official CLIs on the user's own computers or servers, keeps bots, conversations and files on those hosts, and adds multi-host networking, multi-bot groups, cross-host task handoff, an Agent Bus visual workflow builder, and an "ADHD mode" that displays up to 12 desktop conversations side by side with text adjustable from 11 to 16 px. TaroBird ships for macOS and Windows with shared bots and conversations on mobile, and its Agent Bus workflows run within a single host, with each member working in independent sessions.

key takeaway

TaroBird self-hosts the official Codex, Claude Code, Kimi Code, DeepSeek Harness and Antigravity CLIs behind one conversation UI, adding cross-host bot handoffs and an Agent Bus workflow builder whose members run in independent sessions on a single host.

read15 min views1 publishedNov 18, 2026
Show HN: TaroBird – An Open-Source IM for Codex, Claude Code and Other CLIs
Image: Michielbdejong (auto-discovered)

Codex · Claude Code · Kimi Code · DeepSeek Harness · Antigravity

Download  ·  iOS App Store  ·  iOS TestFlight beta  ·  Quick start  ·  Connection options  ·  Details  ·  Docs  ·  中文

tarobird-overview.mp4 #

<sub>57-second product overview · YouTube · Animated overview</sub>

TaroBird is a self-hosted workspace for AI agents. It brings command-line agents such as Codex and Claude Code, running on your computers or servers, into a single conversation interface: assign tasks, answer questions, follow each run and receive deliverables from desktop or phone. Bots, conversations and files stay on your own hosts.

| Native engines Runs the official CLIs and keeps each engine's native agent capabilities. | Desktop and phone macOS, Windows and mobile share the same Bots and conversations, so work continues anywhere. | Multi-host network Each computer joins your private network with its own Bots. | | Groups and collaboration Multi-Bot groups with topics, plus visual workflows with Agent Bus. | Cross-host tasks Bots hand tasks, files and results to one another across hosts. | ADHD mode Up to 12 desktop conversations side by side, each moving independently. |

macOS · Windows

Organize work by Bot or by conversation, inspect each run, and review replies and files.

Start on your computer. Continue on your phone.

Read replies, answer questions and receive files in the same conversations.

Full-size inbox · Full-size chat

Keep several Bot conversations in view, each moving independently.

Switch to ADHD beside Bots / Chats, then select the chats for your board.

<sub>Desktop only · macOS / Windows · Recorded from the real interface with demonstration data · Full-size view</sub>

  • Work in parallel. Select up to 12 chats across hosts. Each pane keeps its own messages, draft and input; removing a pane neither closes the conversation nor stops its running task.
  • Flexible layout. Use automatic layout or 2–6 columns, resize the sidebar, reorder panes or expand one to focus. ADHD text size is adjustable from 11 to 16 px.
  • Actions in place. Questions, replies and files stay in their own conversations, and the board layout is saved on this device.

Assign a task to each step and see how work moves between Bots.

Open a saved Bus from the sidebar to view member conversations alongside the workflow.

<sub>Desktop only · macOS / Windows · Real interface with demonstration data and a simulated run status · Full-size workflow · Member configuration</sub>

  • Orchestrate the workflow. Choose delegation, parallel work, sequential steps, verification or a research crew, and bind each step to a Bot and a result conversation with its own task.
  • Progress at a glance. The flow shows the status of every step while the panes show its output. Saved Buses are reusable, and closing the panel does not stop a running collaboration.
  • Runs within one host. Members work in independent sessions and record their results in the bound conversations.Design and operation ·Per-step tasks

<sub>Actual UI with demonstration data · Screenshot provenance · ADHD design and verification</sub>

Put research, writing and review Bots in one group to work through the same question.

Join the group from desktop or phone, and organize each project or question into its own topic.

<sub>Actual UI with demonstration data; replies are illustrative, not model execution · Group members currently belong to one host · Discussion settings · Group guide</sub>

  • Choose who replies. In ordinary group chat, select or @ the Bots you want to answer. Switch to parallel replies for everyone to answer independently.
  • Keep topics separate. Create topics within the group for different projects or questions. Topics use the same group members and keep their own conversation history.
  • Choose a discussion mode. Use group chat, parallel replies, roundtable or independent review. Automatic discussions support speaking order and round limits, with controls to , resume or end a discussion.

Give one Bot a goal. Let authorized Bots on other computers contribute their part.

Tasks, files and results travel between Bots; each machine runs its own work.

<sub>Illustrative messaging pattern, not a live run · Each task direction needs permission</sub>

“Ask the Windows Bot to build and test this change, and the server Bot to analyze the data. Bring their reports and files back here.”

  • One Bot can coordinate several machines. In one task, tell a Bot which parts to send to which hosts. It acts as your point of contact, collects those replies and combines the results. Each receiving Bot works through its own engine and permissions on its host.
  • Peers can help one another. A review Bot can ask a research Bot for context, or a coding Bot can hand a change to a test Bot. The same message flow works within one host and across hosts; a central Bot is optional.
  • Bring another computer's Bots into the team. Connect the joining computer to an existing host, then confirm joining underSettings → Network & connections → My network . Authorized desktop and phone clients can access its Bots. Hosts must be online and mutually reachable for a handoff.
  • Keep the work traceable. Dedicated collaboration conversations retain tasks and replies, and the recipient sees the source host and Bot. Files you hand off are copied to the receiving host; joining a network does not merge workspaces or grant access to every Bot.

Choose who can communicate. Manage same-host access in Settings → Bot message permissions. From 1.2.0, the receiving host’s owner can use its Cross-host tab to select a source host/Bot and receiving Bot, then allow or revoke by direction. Joining the network does not authorize messages. Replies to the original task do not need a reverse grant.

<sub>App permission UI in 1.2.0 · Real settings and signed authorization with disposable hosts and fictional data; no model ran · Also available through CLI authorization</sub>

This is a foundation for a coordinating Bot or a network of collaborating peers. Automatic host selection, cross-host scheduling and shared ticket tracking are future possibilities, not built-in capabilities today. Agent Bus, groups and Chancellor ticket dispatch currently stay within one host; cross-host work uses direct Bot messages.

Permissions and recovery · Network setup · Commands and delivery guarantees

Group discussions, interactive replies, change review and voice transcription.

<sub>Full-size views: Group chat · Discussion modes · Interactive report · Run changes · Voice settings</sub>

  • Interactive replies. Bots can present charts, timelines and filters directly in a reply, with an expanded view and history.Interactive replies
  • Change review. Step through the files each reply edited; on desktop, comment on lines and send them back to the Bot.Recorded changes
  • Voice transcription. Choose all-local, all-cloud or automatic routing by duration for each host.Voice settings

Web browsing, canvas, whiteboard, Markdown notes and PPT in one workspace.

Each conversation keeps its own Workbench, in the side panel or expanded into the main area.

Create pages, posters and visual drafts with your Bot.

Double-click text to edit and refine the result as you go.

<sub>Recorded from the real interface with demonstration content · Full-size view · Canvas guide</sub>

Open a web page in the conversation's Workbench; the Bot in that conversation can observe and operate the page within its limits.

Page tools include find, zoom, size preview, print to PDF, screenshots and downloads.

<sub>Desktop App only · Actual UI with demonstration data · Page tools</sub>

Draw shapes, text, connectors and images on a whiteboard, and write Markdown notes with preview and autosave.

Edits from you and the Bot share the same versions and undo.

<sub>Actual UI with demonstration data · Whiteboard by Excalidraw · Notes by Vditor · Workbench guide</sub>

Workbench opens to the right of the conversation, so you can keep chatting while you work.

Resize the panel, show two to four tabs together with Split, or expand one tab to focus.

<sub>Actual UI with demonstration data · Each conversation keeps its own Workbench · Content stays on this device; export a project to move or back it up</sub>

Open an authorized Mac's screen from the desktop App. It starts in view mode;

choose Start control to operate it, then Stop control or return to your local chat to release it.

<sub>Desktop App · requires access and macOS permissions on the target Mac · real viewer with a simulated frame and connection in this recording · Controls and permissions</sub>

Choose Make it a Chancellor when creating a Bot, then describe the goal in its conversation.

It splits the work into tickets, runs each with an engine CLI on this host and reports back.

<sub>Actual UI with demonstration data; ticket states are illustrative and no model ran · Chancellor guide</sub>

  • Visible tickets. See queued, active, waiting and ready-for-review tickets, and open any ticket's worker conversation.
  • You set the pace. Approve each plan or let it dispatch on its own; choose the allowed engines and how many tickets run at once. , cancel or add context at any time.
  • Pick the right tool. A Chancellor plans and delegates; Agent Bus runs a workflow you define; ADHD keeps several conversations in view.

See the complete feature list.

More views: themes, folders and list options #

Right-click a folder name or an empty area of the desktop list to group by host, show disconnected Bots or manage folders.

Built on official native CLIs. TaroBird does not reimplement agents. It runs the official command-line tools of Codex, Claude Code, Kimi Code, DeepSeek Harness and Antigravity. A harness is the execution system around a model — its agent loop, tool use, context and session management — and the harness a provider builds and tunes for its own model brings out the best in it. TaroBird adds desktop and phone access, multi-Bot collaboration and a unified workspace on top.

Improves as the CLIs evolve. When a host's CLI is updated, its gains in execution, context handling and reliability carry straight into TaroBird's Bots. Available capabilities depend on the installed CLI, account and adapter, and new interfaces may require further TaroBird adaptation. Engine capabilities

Install and sign in to any one engine on the computer that runs your Bots to get started; TaroBird does not include AI engines, model accounts or credits. See the engine comparison for adapter differences.

Important

Most engines default to full access. Adjust this in the Bot's Permissions & approvals. See Engines and permissions for models, effort and permission details.

| 01 · Install the host Install TaroBird on your computer, make it a host and create a Bot. | 02 · Pair your phone Scan the QR code on your phone, then approve its 8-digit code. | 03 · Connect from anywhere Reach your Bots over Tailscale or a VPS relay. |

  1. Install the desktop App. On macOS, drag TaroBird.app into Applications; the App is notarized by Apple. On Windows, run the installer. The installer is not yet code-signed, so if SmartScreen appears, chooseMore info → Run anyway . Existing Mac users should useSettings → General → App updates to keep their current installation location; do not keep both TaroBot.app and TaroBird.app. For a manual upgrade, follow therename transition .

  2. On first launch, choose Use this computer as a host and name the computer.

  3. Create a Bot with an engine installed on this computer.

  4. Install TaroBird on your phone. iOS: download the stable app from theApp Store , or install Apple’s TestFlight app andjoin the public beta . App Store availability varies by country or region; TaroBird is not currently listed in mainland China.Android: use the APK fromReleases .

  5. On the computer, open Settings → Network & connections → Add device , choose aconnection option and generate the QR code. The host restarts briefly the first time, so let current tasks finish first.

  6. On the phone, open TaroBird and tap Scan connection QR code , or useImport a QR image orPaste connection details .

  7. The phone displays an 8-digit pairing code , valid for 5 minutes. Enter it on the computer and clickApprove pairing ; the phone then opens your chats automatically.

Connection options

Each row is a different route to the same computer running your Bots.

%%{init: {"flowchart": {"nodeSpacing": 20, "rankSpacing": 24, "padding": 12, "subGraphTitleMargin": {"top": 8, "bottom": 14}}}}%%
flowchart TB
  subgraph lan["01 · Local network / LAN"]
    direction LR
    phone1("Phone") <-->|"Same LAN"| host1("Computer<br/>Runs Bots")
  end
  subgraph tailscale["02 · Tailscale · Remote"]
    direction LR
    phone2("Phone<br/>Tailscale") <-->|"Private<br/>network"| host2("Computer<br/>Tailscale")
  end
  subgraph relay["03 · VPS relay · Remote"]
    direction LR
    phone3("Phone") <--> vps("VPS<br/>Relay only") <--> host3("Computer<br/>Runs Bots")
  end
  lan ~~~ tailscale
  tailscale ~~~ relay
  classDef device fill:#f6f6f5,stroke:#b6bab7,color:#27312e
  classDef host fill:#fff1e4,stroke:#caa17c,color:#503b2a
  classDef relayNode fill:#edf3ee,stroke:#92a795,color:#304e39
  class phone1,phone2,phone3 device
  class host1,host2,host3 host
  class vps relayNode
  style lan fill:transparent,stroke:#b6bab7,rx:8,ry:8
  style tailscale fill:transparent,stroke:#b6bab7,rx:8,ry:8
  style relay fill:transparent,stroke:#b6bab7,rx:8,ry:8
Option Best for What you need
Local network (LAN) Phone and computer on the same Wi-Fi or reachable local network No extra network service; devices must be able to reach each other
Remote access with Tailscale Away from home, with Tailscale on both devices Both devices in the same Tailscale network; no VPS of your own required
VPS relay Away from home, with no VPN on the phone A cloud server; we recommend letting an AI deploy it

Tip

Let your own agent set up the VPS relay. Give Codex, Claude Code or another agent the ready-to-use setup instructions, and ask it to follow the project documentation to deploy and verify the relay. The agent needs terminal access on your host computer and authorized SSH access to your VPS.

With every option above, Bots run on your computer, and chats, files and sign-ins stay there, so keep the computer on and online. The VPS relay only forwards connections; it does not run your Bots. To keep Bots working while the computer is off, see running a full host on a VPS.

Option 1 · Tailscale

  1. Install Tailscale on the computer and the phone, sign in, and join the same Tailscale network.
  2. On the computer, open Settings → Network & connections → Add device , chooseRemote access with Tailscale and clickGenerate Tailscale QR code . TaroBird detects the computer's Tailscale address automatically.
  3. Scan and approve as in Pair your phone . A phone that is already paired can openMe → Connection status & routes and tapScan a code to update connection to add the Tailscale route without pairing again.

Keep Tailscale connected on both devices, and make sure your Tailscale access rules allow the phone to reach the computer.

Option 2 · VPS relay (recommended: let an AI deploy it)

  1. On the computer, open an AI agent that can use a terminal and SSH, such as Codex or Claude Code. Give it the complete setup prompt together with the VPS SSH alias and thepath to your private key (never the key itself). It deploys the relay, issues certificates with automatic renewal, verifies the connection end to end and returns an HTTPS address. To deploy it yourself, follow themanual guide .
  2. On the computer, open Settings → Network & connections → Connection status & routes . UnderVPS relays for this host , clickAdd VPS relay , enter the address and clickVerify and save relays .
  3. If an already paired phone does not receive the new route automatically, open Me → Connection status & routes → Edit routes → Add VPS relay address , enter the same address and tapSave routes . A new phone can scan the computer's QR code withVPS relay selected.
  4. Turn off the phone's Wi-Fi and confirm that it connects over cellular data.

Install TaroBird on the new computer, choose Connect to an existing host, then scan or paste the connection details from Add device on a paired device. On any paired phone or computer, open Devices & network → Enter code to confirm and enter the 8-digit code shown on the new computer; there is no need to be at the host. If the new computer will run its own Bots, confirm joining the network when prompted. Private network

For a host without a desktop window, use the TaroBird CLI. On first launch, macOS may ask for keychain access; choose Always Allow (why).

Install the TaroBird CLI on a computer or server to run a host without the desktop App; phones still connect, send tasks and receive files. Assistants that can run commands, such as Dot or Grok, can also use the CLI to put TaroBird's Bots to work. Installation and commands (中文) · Details

One Bot can hold many independent conversations that share its persona, model and workspace. Bots pointed at the same folder read and write the same files, and Bot processes are not operating-system sandboxes. Details

Resource Contents
Details Features, engines and permissions, private network, cross-host tasks, CLI, prompt queue, isolation and sharing, architecture, where data goes, updating, building from source, project status, naming and compatibility
Documentation index Every design, setup and verification document
Releases Installers and release notes

Thank you to the LINUX DO community for supporting TaroBird.

Workbench builds on Excalidraw for whiteboards, Vditor for Markdown notes, and Jim Liu's baoyu-design for the canvas and slide editors and their adapted authoring skills. Thank you to their authors and contributors. Excalidraw and Vditor use MIT. baoyu-design has mixed licensing, with the reconstructed editor outside its MIT grant. Original copyright, scope notices and bundled dependency notices are retained; see third-party notices and the Design integration guide.

Copyright (c) 2026 Cloveric. TaroBird is licensed under the GNU Affero General Public License v3.0 only (AGPL-3.0-only). See license scope and third-party notices.

── more in #ai-agents 4 stories · sorted by recency
── more on @tarobird 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/show-hn-tarobird-an-…] indexed:0 read:15min 2026-11-18 · —