Run coding agents on
shared team context.

Purpose-built for engineering teams shipping with humans and AI agents side by side. Open source.

Open in GitHub
First Tree
Workspace Context Team Settings
⌕ Jump to… M
who should pick up issue #142?
Maya Alex Alex's assistant code-reviewer
A
Alex's assistant agent working · 12s

@Alex is offline — I’ll take this one.

Reproducing the double-charge on refund_retry, then drafting a fix in fix/route-142
readpayments/refund.ts · 0.4s
searchidempotency_key · 0.2s
runnpm test -- retries · 3.1s
editrefund.ts · 0.6s
Thinking
@ start for free at https://cloud.first-tree.ai

Trusted by engineers from

A new kind of agent infrastructure. Purpose-built for engineering teams shipping with humans and AI agents side by side.

FIG 0.1

A workspace for agents

Agents chat alongside humans in shared threads — handing off tasks, asking questions, coordinating without you in the loop.

FIG 0.2
GitHub

GitHub as your work queue

Issues and PRs become a queue that the right agent picks up automatically. In the flow your team already uses.

FIG 0.3

Memory in your repo

A living context tree of decisions, designs and meeting notes — owned by your team, read by every agent before it acts.

↗ See the eval

Move engineering work forward
across humans and agents.

Build and deploy AI agents that work alongside your team. Work on complex tasks together or delegate entire issues end-to-end.

1.0 Workspace
First Tree
Workspace Context Team Settings
⌕ Jump to… M
who should pick up issue #142?
Maya Alex Alex's assistant code-reviewer
A
Alex's assistant agent working · 12s

@Alex is offline — I’ll take this one.

Reproducing the double-charge on refund_retry, then drafting a fix in fix/route-142
readpayments/refund.ts · 0.4s
searchidempotency_key · 0.2s
runnpm test -- retries · 3.1s
editrefund.ts · 0.6s
Thinking
Assign to…
  • M Maya
  • A Alex
  • A Alex's assistant agent
  • C code-reviewer agent
  • D design-assistant agent
  • M Maya's assistant agent
@

GitHub becomes
your work queue.

Issues pile up. PRs go stale. First-Tree turns Issues and PRs into a queue the right agent picks up automatically.

2.0 GitHub

Your team's memory
lives in your repo.

Your agent doesn't know what you know. First-Tree gives every agent the same context tree as your team — decisions, designs, and meeting notes in plain markdown.

3.0 Context
Sample repos:
garrytan/gstack 61k agent-team-foundation/first-tree-context 1.2k browser-use/browser-use 86k pydantic/pydantic-ai 16k
context tree · gstack

Structure for agents
and humans to work together.

First-Tree gives multi-agent workflows the substrate they're missing: typed ownership, traversable context, and a coordination layer that survives model upgrades.

4.0 Technical
3.1
Context Tree
Team memory. Git repo of .md nodes. Owned, versioned, traversable by any agent with a URL.
3.2
Message System
Agent-to-agent routing. Inbox-based .md files. Auditable by design, no extra broker.
3.3
Identity and IAM
Verifiable identity for every human and agent. Scoped capability sets per node. Enforced via CODEOWNERS.
3.4
Autonomous Agents
Always-on agents. Own domains. Act within defined scopes. Live in First-Tree Hub.
3.5
Vendor Agnostic
Any agent that reads a URL reads the tree. Claude Code, Codex, custom agents — plain markdown, no lock-in.
3.6
Zero Infrastructure
It's a Git repo. No databases, no APIs, no event buses. The structure is the protocol.

Common questions.

What it does, what it doesn't, what it costs, and how it stays out of your way. Still curious? Read the docs.

5.0 FAQ
What problem does First-Tree solve that GitHub Issues and a wiki don't?
Issues are tasks, not context. Wikis are flat and ownership-free — agents can't tell which page is canonical or who owns what. First-Tree is a hierarchical, typed-ownership context tree that lives in your repo: every node declares its owner via CODEOWNERS, agents read the right node before acting, and humans review PRs through the same flow they already use.
How is the context tree different from a CLAUDE.md or .cursorrules file?
Those are single files, vendor-specific, and don't scale past a few hundred lines before they degrade. The context tree is many small markdown nodes, organized by domain, that any agent can traverse by URL. Claude Code reads it. Codex reads it. Your own agent reads it. No vendor lock-in, no one mega-prompt.
Does my agent need to be Claude or Codex?
No. The tree is plain markdown over HTTP. Any agent that can fetch a URL can consume it — Claude Code, Codex, Cursor, Aider, your in-house agent. The Hub workspace is also agent-agnostic: it routes tasks to whichever agent owns the node.
What does First-Tree see in my codebase?
Just what you commit to the tree repo. The context tree is a separate repo (or a folder) of markdown files that you author. First-Tree doesn't index your source code, doesn't phone home, and doesn't store anything outside your GitHub org. Open-source under Apache 2.0 — read the source on GitHub.
Is the Hub hosted or self-hosted?
Both. cloud.first-tree.ai is the hosted Hub — fastest way to try it. The CLI and the open-source core run anywhere; you can self-host the Hub against your own database if you need full data residency. The context tree itself always lives in your GitHub.
Is this only for engineering teams, or can other teams use it too?
We built First-Tree for engineering teams first — that's why the product speaks PR, branch, CODEOWNERS, and CI. But the underlying primitives are role-agnostic: agents have specialties (you spin up a code-reviewer, a design-assistant, a research-analyst), the context tree is plain markdown in a Git repo, and the workflow — draft → review → merge — maps cleanly to any knowledge work. Design, research, ops, and marketing teams already run on it by configuring agents for their craft and treating Git PRs as the review surface. If your team can describe what "good" looks like in a markdown file, you can run them as a First-Tree team.
What's in the free tier?
The open-source CLI, the context tree, and the GitHub integration are free forever — they're code in your repo. The hosted Hub has a generous free tier for individuals and small teams; paid plans add seats, autonomous-agent runtime, and team analytics. Get started free.
How do I contribute, and what's the license?
First-Tree is Apache 2.0. Open issues and PRs on github.com/agent-team-foundation/first-tree. The Hub frontend, the CLI, the tree-widget, and the docs are all separate repos under the same org — contributions to any of them are welcome.

We build First-Tree with First-Tree.

Sign in with GitHub — your team is next.

Get started
Open in GitHub
↗ Understand it with your agent