Core Concepts

Message Graph

We have primarily these types of nodes in the Agentree graph:

• Conversation nodes
• Commit nodes
• File nodes (Upcoming)

Conversation nodes can be user or assistant. Commit nodes can either represent Agentree generated commits or external commits that Agentree imported in the graph.

Turn

A turn represents a single user request, the assistant run that responds to it and commit if assistant made any code changes.

Threads

Best way to think about threads is "tasks". Create one thread per task, keep all explorations around that task in that thread. Close it once you are finished.

Sometimes you start a thread with a single task in mind, but as you do the exploration, you might end up working on what might be multiple long tasks in the same thread. For such cases, to keep the graph maintainable, Agentree has a feature that allows you to convert subgraphs into new threads, so in the original thread a thread node would be created at that position.

Branching

Branching creates a new path from an existing message. To branch, you can just click on any message and send a message from that.

You can also use the hovercard's quick reply feature.

Worktrees

Agentree creates worktrees for each agent run to keep work of all agents isolated. That keeps parallel experiments from colliding at the filesystem level.

Hovercards

Hovercards show message context without taking you out of the graph. Use them to inspect a node, compare nearby reasoning, or decide where to branch next.

Composer

The composer is where you write prompts, choose model, and send work to an agent.

Optionally, you can also choose base commit and filter context to be sent to agent in composer.

Agentree MCP

Agentree creates an MCP server that allows agents use to inspect Agentree's graph themselves. It exposes tools for reading nodes, threads, commits, graph diffs, and workspace overview while keeping the agent connected to the current workspace. It's extremely helpful for agents to check past work and get full context of 'why' behind code.

Merge Panel

When you feel commit is ready, you can add it to merge panel. After you've added multiple commits to merge panel from various threads and sessions, you can ask AI agent to review and merge the commits. It'll merge them to selected target branch using octopus merge.

Flows

Flows are predefined multi-agent workflows that run structured sequences of agent tasks, such as parallel implementation, review, and merge preparation.