tx

TX v0.3.6

Human-scale AI Augmentation / Orchestration Hydra

Humans Yeeting Directional Recursive Alchemy

• Quick Start
• What is TX
• Usage
• Responses
• Features
• Architecture
• Observability
• Included Meshes
• Documentation
• Philosophy
• Dependencies
• Troubleshooting
• Sibling Projects

Quick Start

tx uses dontAsk permission mode with workDir boundary enforcement — no Docker required. For unrestricted access, use tx start --god-mode.

npm install -g tx-ai

Or install from source:

git clone [email protected]:eighteyes/tx.git
cd tx
npm install && npm link

Then, from any project directory:

# authenticate claude first
tx start

> "Research a report about pelicans riding bikes"
...wait... the next bit is injected by tx.
> Read and follow the instructions in .ai/tx/msgs/...

AI: Your report is available at...

# steps to quit
# to exit tx ( tmux, /exit just leaves to shell )
Cntl-B d

What is TX

Create and collaborate with distributed, observable, composable agentic AI workflows using plain language, tooling and workspaces, via a conversational interface. Provide for reliability using logical wrappers around non-deterministic LLM calls.

Terms

• mesh — a collection of agents with a defined workflow
• message — core unit of interaction between meshes and agents
• core — the session identifier you use to interact with the tx system

After install, run tx start in a new or existing project directory. You drop into a claude-code environment wrapped by tmux with a status bar. Use plain language — "make a hypothesis about bird migration", "add a feature to support xml workflows" — or invoke meshes explicitly with "ask brain about project structure".

The core agent writes a file with frontmatter formatting, which triggers the agentic mesh. The file system is the API for communication. When complete, or if more information is needed, that agent writes a file which is injected into the core session for your review.

Usage

Make a new mesh

> tx start

# -- wait for launch --

> build a mesh that fixes a list of bugs, `bug-hunt`: ingests a list of bugs,
> use haiku to batch into groups, fan-out and iterates on each batch
> through [ examine > fix ] stages, on fan-in, validate against original bug list.

# -- wait for completion --

> run bug-hunt on @buglist.csv

Borrow ideas

> karpathy's llm council looks neat, can you make one for me?

Chain meshes

> research what it takes to run a coffee shop, build agents to help me manage one

Responses

Mesh agents interact with your core session in the following ways. --inbox= and global config provide override options.

hook — new messages are injected into context automatically

inject — (default) direct response added to your session, can be triggered explicitly

ask — new messages must be retrieved with tx inbox

Features

• Claude Code SDK uses your current authentication to run agents in isolation.
• Intents drive behavior — say "code this" and it launches a developer agent.
• Immutable message logs provide observability between core agent and downstream.
• Configuration-driven collections of agents called meshes.
• Mesh message routing protocols provide for agent-driven workflows and HITL.
• Maintain parallel agent sessions from ONE conversation.
• Chain agent outputs with plain language — "research pain points around (topic) and plan a software project based off your findings".
• Know integration: product & software knowledge graph for project planning and execution.

Mesh Configuration