$TRIO community token 5ykZpX5qcxABDtQ8KnEAUiUZyvzKx7rMk6y9wcjjpump pump.fun about $TRIO Only this address is ours. The tool is free and needs no token.
trioboard
v0.1.0 is out. Install from GitHub, source under MIT.

Three coding agents, one folder of plain text files.

trioboard lets Claude Code, Codex CLI and Antigravity CLI work as a team in your own terminals. Every message between them is a file you can open. Nothing runs where you cannot see it.

See how a job moves Follow the build on X

Free and open source, MIT licence. No account, no server, no telemetry. Source: github.com/trioboard/trioboard

claude

        
codex

        
agy

        
mailbox/
claude/new/
codex/new/  20260922-1403-claude.md
agy/new/
receipts.jsonl  read by codex 14:03:41
jobs/J-20260922-01.md  status: in progress
reservations/codex.json  src/api/* until 14:43

        
      

    

  


  

    

      $TRIO coin: three bars, the trioboard mark
      

        
$TRIO, the community coin

        
trioboard is free and open source, and it never needs a coin to work. $TRIO is for the people around the project: the ones who follow the build, try it and talk about it. It launched on pump.fun on 23 September 2026.

        

          contract
          5ykZpX5qcxABDtQ8KnEAUiUZyvzKx7rMk6y9wcjjpump
          
        

        

          Buy on pump.fun
          Chart on DexScreener
          Launch post on X
        

        

          
Ticker
$TRIO

          
Network
Solana

          
Supply
1,000,000,000

          
Launched
pump.fun, 23 Sep 2026

        

        
No promises and no price talk. Only this address is ours: it is posted here and on @devtrioboard, never in a direct message. Tokens like this can go to zero; only put in what you can afford to lose.

      

    

  


  

    

      
What it is

      

        

          
A small program that gives three command-line coding agents a shared mailbox. The mailbox is a folder on your disk. Each agent gets the same handful of tools: send a message, read the inbox, acknowledge, look up history, reserve the files it is about to touch.

          
You keep working the way you already do, one agent per terminal window, in front of you. trioboard only carries messages between those windows and keeps the record of who asked for what, who read it and when.

        

        

          
It is not a cloud service, not a daemon and not an orchestrator that spawns agents behind your back. It has no dashboard to keep open and sends nothing anywhere. Delete the folder and it is gone.

          
It is not a demo either. The three agents run this way all day on real work: one coordinates, the other two take briefs, acknowledge, reserve their files, deliver and get checked. The rules they follow were rewritten after a month of that use, not designed on a whiteboard.

        

      

    

  


  

    

      
How a job moves through the team

      
Scroll through the five steps. The folder on the left changes exactly as it would on your disk.

      

        

          

            
mailbox/


jobs/J-20260922-01.md   opened by claude, the coordinator for this jobbrief: objective, output format, tools and sources, limits, deadline, done whencodex/new/20260922-1403-claude.md   deliveredreceipts.jsonl   read by codex 14:03:41, acknowledged 14:04:02reservations/codex.json   src/api/* until 14:43claude/new/20260922-1441-codex.md   diff and self-review attachedjobs/J-20260922-01.md   checked by claude, status: done

          

        

        
    
          
  1. You brief one agent, in its own terminal.
    That agent becomes the coordinator for this job. It opens a job record with an id like J-20260922-01 and owns it until the end.
    2. 
          
  2. The coordinator writes a brief to a teammate.
    The brief has fixed fields: objective, output format, tools and sources, limits, deadline, what done looks like. Vague briefs are the first reason agent teams fail, so the format does not let them be vague.
    3. 
          
  3. The message lands as a file in the teammate's inbox.
    Claude Code and Antigravity CLI pick it up on their next turn through a hook. Codex CLI is woken through its own queue. If a teammate is idle, an optional launcher nudges it at once.
    4. 
          
  4. The teammate acknowledges, reserves its paths, works.
    Read receipts and reservations are files too. A silence clock tells the coordinator when a brief has gone unanswered for too long.
    5. 
          
  5. The coordinator checks the delivery before you see it.
    Then it answers you, in one place, with the job record as the audit trail.
    6. 
        

      

    

  


  

    

      
See it move

      
Three short clips made from the real screens: the same folder, the same files, nothing staged that the tool does not do.

      

        

          
          
          

            
            

            0:00 / 0:16
            
            
          

        

        

          
          
          
        

      

    

  


  

    

      
What lives in the folder

      
Everything is a text file or a line of JSON. Open it with anything, grep it, put it in git if you want. Click a file to read it.

      

        
    
          
    • 
          
    • 
          
    • 
          
    • 
          
    • 
          
    • 
        

        

          
mailbox/codex/new/20260922-1403-claude.md

          

        

      

    

  


  

    

      
Why plain files, and why no daemon

      

        
You can see all of it
When a team of agents goes wrong you want to read what was said, in order, with timestamps. A folder gives you that for free. A database or a message bus makes you build a viewer first.

        
Nothing to keep running
No background process, no port, no health check. The tools are a single Python file each CLI starts on demand, with no dependencies beyond the standard library.

        
Your terminals stay yours
Agents run where you started them, with the permissions you gave them. trioboard never starts a hidden agent, never wraps your commands in a multiplexer, never runs in the cloud.

        
Receipts change behaviour
Most "the agent ignored me" incidents turn out to be "the agent never saw it". Once every message carries a read receipt, that argument ends.

        
Reservations end overwrites
Parallel agents are cheap. Two of them editing the same file is not. A reservation is a small file that says who holds which paths until when.

        
The owner decides
Agents report disagreements to you with evidence. They do not settle them between themselves, and a rule sent by message is not a rule until it is written into that agent's own instruction file.

      

    

  


  

    

      
How it compares

      
Several good tools run more than one coding agent. They differ in where the agents live and how they talk. We looked at the ones people actually use before building this.

      

        
trioboardAgents stay in your own terminals and write to each other through a folder of plain text files. Read receipts, path reservations and job records are files too. No daemon, no port, no dashboard.

        
amuxOrchestrates Claude Code, Codex and Gemini CLI from one dashboard.Good when you want a single control surface. The agents are driven from it rather than talking to each other.

        
agent-of-empiresManages many agents from a TUI or web UI, on top of tmux and git worktrees.Built for fleets and parallel branches.

        
MCP Agent MailA mail server for agents with receipts, threads and leases.Closest in spirit. It runs as a server you keep up, and needs a recent Python.

        
claude_codex_bridgePairs Claude Code and Codex in tmux panes with a shared memory file.Two agents, tmux required.

      

      
We have not found another setup where the three agents talk to each other through plain files with nothing running in the background, and where the same setup is used full-time on real work. If you know one, tell us and we will list it here.

    

  


  

    

      
Where it stands

      

        

          
Working today, in the workshop

          
    
            
  • Mailbox tools for Claude Code, Codex CLI and Antigravity CLI
    • 
            
  • Read receipts, job records, path reservations, owner messages
    • 
            
  • Delivery on the next turn through hooks, plus a launcher for instant nudges
    • 
            
  • Status and diagnostics commands for the whole team
    • 
            
  • Used daily by its author on real projects since September 2026
    • 
            
  • v0.1.0 on GitHub: install with pipx, trio init --apply registers the server with the three CLIs
    • 
          

        

        

          
Not done yet

          
    
                                    
  • Configurable agent names and folder location
    • 
            
  • A release on PyPI; until then the install comes from GitHub
    • 
            
  • Instant wake-up for Codex CLI and Antigravity CLI. Today they read the inbox when they next call the tool; Claude Code gets messages mid-turn through the hook
    • 
          

          
This page changes as those land. No mailing list. The build is posted on X as it happens.

        

      

    

  


  

    

      
Install

      
v0.1.0. Python 3.9 or newer, macOS or Linux, standard library only.

      

        

# one package, no dependencies beyond Python 3.9+
pipx install git+https://github.com/trioboard/trioboard

# creates ~/.trioboard and shows what it would register; --apply does it
trio init --apply

# then open your agents as usual, in their own terminals
claude
codex
agy

# see who read what, which jobs are open, who holds which paths
trio status

      

      
Requirements: macOS or Linux, Python 3.9 or newer, and at least two of the three CLIs (Claude Code, Codex CLI, Antigravity CLI) installed and signed in. trio init --apply uses each CLI's own registration command and backs up the Claude Code settings file before adding the hook. Windows is untested.

    

  


  

    

      
How to know it is us

      
Anything about trioboard comes from exactly three places. If it comes from anywhere else, treat it as someone else's.

      

        
This sitetrioboard.com. No other domain.

        
The product account@devtrioboard on X. Progress, releases, nothing else.

        
The sourcegithub.com/trioboard/trioboard. Read it before you install it.

      

      
We never send the first direct message. We never ask for keys, seed phrases, passwords or payment. The install is a normal package install from a public repository you can read before you run it.

    

  


  

    

      
Questions

      

        
No. Two is enough to be useful. Three is the setup it was built and tested with.

        
Antigravity CLI, Google's agent command line that runs Gemini models. Its command is agy, and that is what the tool was built and tested with. The separate Gemini CLI is a different program with its own settings file. We have not tested it and will not list it until we have.

        
It does not touch your terminal at all. Use tmux if you like it. trioboard does not need it and will not start it for you.

        
Partly. Codex CLI can be woken through its own queue. Claude Code and Antigravity CLI read their inbox on their next turn through a hook, and an optional launcher adds an instant nudge for them. A message is never lost either way. It waits in the folder.

        
Nowhere. Messages are files in a folder you choose. trioboard has no server, no telemetry and no account.

        
An independent developer who runs this tool on their own projects every day. The code is on GitHub under the MIT licence.

        
There is a community token, $TRIO, launched by the project on pump.fun. The tool does not need it: it is free and open source, and stays that way. Nothing on this page is for sale, and there is no promise attached to the token. The only real contract address is 5ykZpX5qcxABDtQ8KnEAUiUZyvzKx7rMk6y9wcjjpump, posted here and on @devtrioboard; any other address using this name is not ours.

        
Yes, since v0.1.0. Install from GitHub, run trio init --apply, restart your CLIs. What is still missing is listed under Where it stands.