N-Tree Studios

Grove by N-Tree Studios

A Software Engineering Workbench, where you design the schematic, the profiles, the task lists and the playbooks. Your sessions inherit them, along with the rules they must follow and the evidence they must provide.

  1. Grove's sessions view listing seventeen sessions, most of them active. Three assistant sessions each have the sessions they spawned indented beneath them, and every row carries its task progress, the profile and harness it inherited, the project it is working in, whether its working tree is clean or has uncommitted work, and its age.
    The Sessions
  2. Grove's sessions view with the queue drawer open beside it. Eleven sessions are listed with their status, profile, runtime and harness, three of them nested under the assistant that spawned them. The drawer reads eight sessions waiting on capacity, each row numbered with controls to move it up or down the queue, force-launch it past the limit, or remove it.
    The Queue
  3. Grove's projects view listing twenty-four repositories with search and filters above them. Each row carries its branch, its last merged pull request, whether it is in sync and whether it has uncommitted work, with actions to view it or open a session, and one of them shows the live session running in it.
    The Projects
  4. A session open on its Tasks tab. Two tasks for happy-path and error-path tests each read that two of two expectations are unmet, above a command-output expectation naming what the test output must show and a written-note expectation naming what must be explained, each with an action to attach evidence. A third task carries three checks that gate on a clean exit.
    The Checks
  5. An executive summary open on an archived session. The report's contents run down the left as seven numbered sections, from showing the change in code through to opening a pull request, with the third selected. Beside it two image blocks sit one above the other, each holding a screenshot of the same settings screen in the same framing and a collapsed explanation.
    The Executive Summary
  6. A session's executive summary open on the fourth of eight sections. The report contents run down the left, from reproducing the bug through to opening a pull request. Beside them a block of source is shown with one line marked and an explanation of the change written against it, and below that a command block reporting three hundred and fifty-three test files and three thousand five hundred and twenty-three tests passed, exiting zero.
    The Evidence
  7. Grove's preview browser with this website loaded and comment mode switched on: a numbered marker sits on the page and the Review tab below lists the comment it opened, which becomes a task on the agent's list.
    The Preview Browser
  8. Grove's Add boundary form: a scope of global, a tool name, a decision of deny, a match pattern testing the call's command field against a regular expression, a source directory condition, and a response field for what the agent is told.
    The Boundaries

Grove

The Features

Sessions

Sessions
One agent, one copy of the repository.
Session queue
Set a cap, queue the rest.
Assistant sessions
A session that runs other sessions.
Managed sessions
One session answers for another.
Preview browser
A browser in every session.
Branch review
The whole branch as one diff.

Studio

Schematics
Your system, drawn as a typed graph.
Lexicons
The vocabulary a design may use.
Playbooks
Skills, rules and setup, versioned together.
Profiles
A preset a session starts from.
Task lists
A checklist with a definition of done.
Program runs
A playbook that runs as steps.
Validators and targets
Rules about the design, run together.
Audit targets
Generated files checked against the design.
Query console
Query the design.
Studio assistant
Answers questions about the open design.

Evidence

Command checks
Cannot close while its command fails.
Before and after
The same screen, before and after.
Recorded walkthroughs
The agent records the flow working.
Executive summary
One numbered report per session.
User sign-off
Only a named person can close it.

Permissions

Boundaries
A standing rule: allow, deny, or ask.
Boundary assistant
Ask what your boundaries actually permit.
Approvals
Decide once, or make it a boundary.

Design

The Studio

A typed graph, validated by machine with no model in the path, and an audit that compares every generated file on disk against what the design would render now.

A playbook, and the run it declares

A program playbook open on its run graph, headed seven steps and seven deep with a longest chain of seven and one step that waits on a person. Five step cards run left to right across the start and four following stages, four of them tool steps and one a gate carrying the condition it branches on.

The design as a graph, by depth

Grove Studio showing a review pipeline as a typed graph, twenty-six nodes laid out left to right across eleven depth bands, from a manifest at depth zero through steps, gates, tools and processors to the parameters they take.

One dependency path through it

The same graph zoomed into four nodes, with the dependency path between a step, the step it depends on and the form it opens drawn as a dashed line.

Everything one node reaches

A step selected, with a panel listing its fields and relations, and a choice between showing direct impact and the full chain.

Swimlanes, one lane per type

The same model drawn as swimlanes, one lane per node type, reading thirteen lanes and twenty-six nodes across depths zero to ten.

A board, grouped by type

The same model as a board grouped by type, with columns for steps, parameters, processors and session steps, each card showing how many relations come in and go out.

A table, opened on one node

A sortable table of every node, with a processor row expanded, its four parameters listed beneath it, and a panel showing the processor definition including the command it runs.

Pricing

What Grove costs.

Monthly

$30

per seat, per month

Get Grove

Annual Two months free

$300

per seat, per year

Get Grove

Enterprise

Custom

minimum 50 seats

Contact us

Compatible with:

  • Claude Code
  • Codex
  • GitHub Copilot
  • Model Gateway (OpenRouter)

N-Tree Studios

We are customer zero.

We started N-Tree Studios to build the tools we needed, then built them in Grove. We use it every day, on just about everything: the product itself, the account platform, this website, and our back office.

Meet the founders