tx
Primitives, not frameworks. Headless infrastructure for memory, tasks, and orchestration.
The Problem
Your agents lose context between sessions. Tasks collide when multiple agents work in parallel. Learnings vanish into conversation history. You're rebuilding the same infrastructure every project.
The Solution
Composable primitives that handle the hard parts. You keep control of the orchestration.
┌─────────────────────────────────────────────────────────┐
│ Your Orchestration (your code, your rules) │
├─────────────────────────────────────────────────────────┤
│ tx primitives │
│ │
│ tx ready tx done tx context tx learn │
│ tx claim tx block tx sync tx trace │
│ │
└─────────────────────────────────────────────────────────┘Why Primitives?
The orchestration flow is where you create value. It encodes your domain knowledge:
- How your codebase works
- What your agents are good at
- Where humans need to intervene
- How you handle failures
If we dictate the flow, we're not a tool. We're a competitor. We don't know your domain, your constraints, or whether you need 3 agents or 30.
TanStack won by saying: "Here's headless table logic. Style it yourself."
tx says: "Here's headless agent infrastructure. Orchestrate it yourself."
Core Primitives
| Primitive | Purpose |
|---|---|
tx ready | Get next workable task (unblocked, highest priority) |
tx done | Complete task, potentially unblocking others |
tx block | Declare dependencies between tasks |
tx claim | Claim task with lease to prevent parallel collisions |
tx context | Get relevant learnings for prompt injection |
tx learning:* | Record and search knowledge |
tx sync | Persist to git-friendly JSONL |
tx try / tx attempts | Record and track implementation attempts |
tx doc * | Docs-as-primitives with YAML structured documentation |
tx invariant * | Machine-checkable system rules with enforcement tracking |
tx trace * | Execution tracing and run observability |
tx cycle | Sub-agent swarm scanning for issue discovery |
Get Started
Ready to dive in? Follow the Getting Started guide to install tx and run your first task loop.
Design Principles
- No opinions on orchestration. Serial, parallel, swarm, human-in-loop. Your call.
- Powerful defaults.
tx readyjust works. So does dependency resolution. - Escape hatches everywhere. Raw SQL access, JSONL export, custom scoring.
- Framework agnostic. CLI, MCP, REST API, TypeScript SDK. Use what fits.
- Local-first. SQLite + git. No server required. Works offline.
Interfaces
| Interface | Use Case |
|---|---|
| CLI | Scripts, terminal workflows, agent loops |
| MCP Server | Claude Code integration (42 tools) |
| REST API | Custom dashboards, external integrations |
| TypeScript SDK | Programmatic access from your agents |
| Dashboard | Visual monitoring and management |
License
MIT