Skip to main content
Glama

Gantry

A shared place for people and agents to develop robot hardware and software.

Keep working in your CAD tools, editor and simulator. Use Gantry to share unfinished changes, preserve their context, and let another person or agent continue from the same version.

Try the demo · Get started · Tool support · Documentation

The website and demo source includes local preview and test instructions.

The demo uses invented, browser-only data. Local operation is the supported starting point. The latest packaged release is v3.4.2, including guided project onboarding and contextual Studio Bot work.

How it works

flowchart LR
    A["Your tools and agents<br/>CAD · Code · Simulation"] -->|Capture saved work| B["Gantry Ledger<br/>Versions · Requirements · Evidence"]
    B -->|Restore and continue| A
    B <-->|Shared changes and discussions| C["Your team<br/>Studio · CLI · MCP"]
  1. Bring existing work. Select saved files from a project already in progress.

  2. Share a checkpoint. Keep the changes, reasons, requirements and unfinished work together.

  3. Discuss or review. Refer to a specific artifact version, CAD part or code line.

  4. Continue. Restore the shared state, make the next change, and retain its evidence.

Sharing, passing a check and formally adopting a design are separate actions. An old test result never becomes a pass for a new combination of files.

Related MCP server: Nolane Habitat

Choose how to use Gantry

Both options use the same development history. You can start with Ledger alone.

Gantry Ledger

Gantry Crew

Use it to

Share and review development state

Delegate development to a persistent Bot team

Who drives the work?

Your team and its existing agents

Bots with assigned roles and delegated authority

Main capabilities

Versions, requirements, discussions, evidence, optional Mentor review

Role memory, consultation, hierarchical delegation and handoffs

Entry point

gantry-ledger

gantry-crew

Guide

Ledger setup

Crew setup

Mentor reviews submitted changes and proposes follow-up work. Crew Bots reason and act within their roles; Mentor is not their manager. Core stores the decisions and enforces access and version integrity—it does not choose the best engineering design.

You supply the agent runtime and model account. No inference provider is enabled by default, and storing development state needs no model account.

Get started

Connect your local agent

Use patched Python 3.11+ on macOS or Linux. Before installing, follow the runtime and installer security guide, including its hash-pinned pip bootstrap.

git clone https://github.com/fourn9/gantry-oss.git
cd gantry-oss
python3 -m venv .venv
# Apply the installer updates described in the security guide above.
.venv/bin/python -m pip install .
.venv/bin/python -m gantry.security_check

.venv/bin/gantry connect /path/to/your/project --client codex \
  --path src/ --path tests/ --write-path src/ \
  --goal "Improve request clamping" \
  --done "Existing boundary tests pass without changing their assertions"

Review and confirm the permission plan: selected files, writable scope, test commands and completion conditions. Gantry creates the local ledger and scoped identities, captures saved files, and adds its project MCP entry. Client trust settings remain under your control.

  • Choose --client claude, cursor or generic for another client.

  • The default permits scoped work. Choose --mode record-only to record externally edited files instead.

  • This local route needs no separately operated server. Tests are refused when a supported command sandbox is unavailable.

Full setup and daily commands →

Share work in Studio

For a visual workspace, follow Studio setup, then choose Import project:

Select files → Review scope → Clarify components → Open first work → Share update

Guided setup preserves answers and corrections across interruptions. Agent interpretation is optional; it does not execute the project or approve its design.

Studio keeps the product structure and team work together, with CAD, Code and Checks tabs. Conversations stay attached to their target and version. Another authorized participant can restore a shared version into a separate workspace.

Open Team to configure persistent Bot roles and customer runtimes. From a work, CAD part or code line, Ask a Bot queues a read-only question; Assign work queues a scoped edit. Answers return to the original conversation and Inbox; edits return as separate shared candidates. Browsing or mentioning a Bot does not start it. Studio Bot setup and handoff →

Guided onboarding · Sync, share and continue · Self-hosting and membership

What stays with the work

Saved information

What it enables

Artifact snapshots and development states

Restore the exact saved files and their context

Requirements, changes and declared dependencies

Trace the purpose of a change and what needs reassessment

Evaluations tied to input versions

Distinguish current evidence from obsolete or missing checks

Discussions, decisions and alternatives

Understand why a choice was made and what remains unresolved

Bot roles, experience and execution journals

Carry context into later work and recover supported interrupted operations

Gantry preserves original captured data. It does not infer complete cross-tool dependencies or certify physical safety. Native editing and engineering validation still require the appropriate tools and evidence.

Tool support

Capture, editing and live synchronization are different capabilities. Check the exact route before adopting an integration.

Route

Available today

Boundary

Saved files and Git

Versioned capture, restoration, explicit sync and sharing

Only captured scope; unsaved edits are not included

GitHub and external records

Issue, PR and CI ingestion; bounded readers and saved exports

Authentication and capture coverage depend on the connector

Headless OCP / STEP

Optional local read, edit, write and static interference checks

Not a universal CAD editor or physical-validity guarantee

Strength, tolerance and prototype results

Evidence capture against a frozen acceptance plan

Requires an actual evaluator or measured input

Commercial CAD / ECAD

Experimental desktop operations and generated editor scripts

No verified live run for the eight listed vendor products; Zuken and Capital SDK implementations remain blocked

Integration coverage · Native desktop support · Hardware adapter

  • Local workspace capture supports up to 10,000 files / 1 GiB with frozen, resumable uploads. Guided browser onboarding supports 1,000 files / 32 MiB, at most 16 MiB per file.

  • Watching saved files is opt-in. It never shares or formally adopts changes automatically.

  • Local reviews and tests have no Gantry count cap. Scope, revocation, command timeouts, branch limits and provider limits still apply. Existing finite credentials retain their approved expiry.

  • Default Mentor review uses your client through structured prepare/finish tools. It does not automatically launch an independent reviewer. Subscription-based review is an explicit opt-in.

  • Single-host deployment and backup/restore procedures are provided. They do not provision a cloud account, email invitations or enable paid inference.

  • Native-runtime qualification, broader physical validity and engineering speedup remain separate from functional tests.

Recovery · Executed acceptance and limits

Documentation

Browse all guides · Examples · Verification records

I want to…

Read

Connect an agent and review a change

Agent setup

Import, share or restore a project

Guided onboarding · Connected workspaces

Link requirements, changes and checks

Requirement traceability · Design change loop

Configure a Bot organization

Studio team onboarding · CLI onboarding · Crew organization · Persistent Bots

Use and evaluate Bot experience

Learning · Continuity · Paired evaluation

Connect engineering tools

Engineering workflow · External write plans

Operate a shared deployment

Cloud operations · Advanced administration

Understand the architecture

Architecture · Ledger / Crew boundary

Privacy and contributions

Feedback is off by default. You may opt into statistics and individually selected diagnostics. Nothing is sent in the background; every encrypted upload requires preview confirmation. No public receiver is preconfigured.

Privacy · Security policy · Optional encrypted feedback

Report issues, propose adapters or contribute tests. Use minimal synthetic examples—never confidential CAD, source, logs or credentials.

.venv/bin/python -m pip install ".[feedback]"
.venv/bin/python -m unittest discover -s tests -p 'test_*.py' -q
node --test tests/test_*.mjs

Core tests use the standard library. Optional NumPy and CAD tests skip when dependencies are absent. Use GANTRY_CAD_PYTHON to select a separate interpreter with Gantry [cad] installed.

Contributing guide · Synthetic end-to-end example

License

MIT. The published source, including Core and Mentor orchestration, may be used, modified and redistributed. Third-party tools and models retain their own licenses and terms.

Available Tools

52 tools
bot_inboxD
Read-only

bot inbox

Inputs: arguments (required), idempotency_key.

contextB
Read-only

Read work context. Full is unchanged. Focused requires entry_ids, follows declared dependencies in the fixed design, and pages related discussion. Explicit omissions are not an impact analysis or approval.

Inputs: arguments (required), idempotency_key.

designD
Read-only

design

Inputs: arguments (required), idempotency_key.

development_stateD
Read-only

development state

Inputs: arguments (required), idempotency_key.

eventsC
Read-only

Poll durable notices from a ledger sequence cursor; deduplicate by event_id.

Inputs: arguments (required), idempotency_key.

get_bot_contextD
Read-only

get bot context

Inputs: arguments (required), idempotency_key.

get_bot_issueD
Read-only

get bot issue

Inputs: arguments (required), idempotency_key.

get_change_reviewD
Read-only

get change review

Inputs: arguments (required), idempotency_key.

get_crew_setupD
Read-only

get crew setup

Inputs: arguments (required), idempotency_key.

get_design_assessmentD
Read-only

get design assessment

Inputs: arguments (required), idempotency_key.

get_development_stateD
Read-only

get development state

Inputs: arguments (required), idempotency_key.

get_evidence_viewD
Read-only

get evidence view

Inputs: arguments (required), idempotency_key.

get_onboardingC
Read-only

Read bounded discovery, exact source manifest, prior answers and the customer-agent contract.

Inputs: arguments (required), idempotency_key.

get_persistent_botD
Read-only

get persistent bot

Inputs: arguments (required), idempotency_key.

get_review_teamD
Read-only

get review team

Inputs: arguments (required), idempotency_key.

get_team_proposalD
Read-only

get team proposal

Inputs: arguments (required), idempotency_key.

get_validation_planD
Read-only

get validation plan

Inputs: arguments (required), idempotency_key.

historyD
Read-only

history

Inputs: arguments (required), idempotency_key.

identityC
Read-only

Read the authenticated identity, without credentials.

Inputs: arguments (required), idempotency_key.

impactD
Read-only

impact

Inputs: arguments (required), idempotency_key.

list_artifact_filesD
Read-only

list artifact files

Inputs: arguments (required), idempotency_key.

list_bot_issuesD
Read-only

list bot issues

Inputs: arguments (required), idempotency_key.

list_bot_memoriesD
Read-only

list bot memories

Inputs: arguments (required), idempotency_key.

list_change_reviewsD
Read-only

list change reviews

Inputs: arguments (required), idempotency_key.

list_crew_setupsD
Read-only

list crew setups

Inputs: arguments (required), idempotency_key.

list_development_statesD
Read-only

list development states

Inputs: arguments (required), idempotency_key.

list_onboardingsD
Read-only

list onboardings

Inputs: arguments (required), idempotency_key.

list_persistent_memoriesD
Read-only

list persistent memories

Inputs: arguments (required), idempotency_key.

list_team_messagesD
Read-only

list team messages

Inputs: arguments (required), idempotency_key.

openD
Read-only

open

Inputs: arguments (required), idempotency_key.

outcomesD
Read-only

outcomes

Inputs: arguments (required), idempotency_key.

product_overviewD
Read-only

product overview

Inputs: arguments (required), idempotency_key.

project_detailsD
Read-only

project details

Inputs: arguments (required), idempotency_key.

query_evidenceD
Read-only

query evidence

Inputs: arguments (required), idempotency_key.

read_artifact_batchD
Read-only

read artifact batch

Inputs: arguments (required), idempotency_key.

read_artifact_chunkB
Read-only

Read one hash-verified part, at most 32 MiB. Ordinary files have only index 0.

Inputs: arguments (required), idempotency_key.

render_evidence_viewD
Read-only

render evidence view

Inputs: arguments (required), idempotency_key.

restore_artifactB
Read-only

Return saved bytes or metadata_only manifest. Chunked files require read_artifact_chunk; hashes cover each part and the complete file.

Inputs: arguments (required), idempotency_key.

review_automation_statusD
Read-only

review automation status

Inputs: arguments (required), idempotency_key.

review_contextB
Read-only

Read a consistent snapshot of the candidate diff, evidence, evaluations, work and review permissions.

Inputs: arguments (required), idempotency_key.

reviewsD
Read-only

reviews

Inputs: arguments (required), idempotency_key.

session_detailsD
Read-only

session details

Inputs: arguments (required), idempotency_key.

stateD
Read-only

state

Inputs: arguments (required), idempotency_key.

studio_contextD
Read-only

studio context

Inputs: arguments (required), idempotency_key.

studio_inboxD
Read-only

studio inbox

Inputs: arguments (required), idempotency_key.

studio_libraryD
Read-only

studio library

Inputs: arguments (required), idempotency_key.

studio_overviewD
Read-only

studio overview

Inputs: arguments (required), idempotency_key.

studio_teamD
Read-only

studio team

Inputs: arguments (required), idempotency_key.

studio_workD
Read-only

studio work

Inputs: arguments (required), idempotency_key.

whyD
Read-only

why

Inputs: arguments (required), idempotency_key.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    D1.6/5.0

    Scored across 52 tools

    Disambiguation2/5

    Several tools appear to target the same thing: get_development_state vs. development_state vs. list_development_states, get_design_assessment vs. design, get_bot_context vs. bot_inbox vs. get_persistent_bot, and a dense cluster of review tools (reviews, get_change_review, list_change_reviews, review_context, related_review_context, review_automation_status). Many tools have no description beyond their own name (open, why, design, state, impact, outcomes), so an agent has almost nothing to separate them by. A few areas (artifact reading, evidence) are distinguishable, but the duplication dominates.

    Naming Consistency2/5

    The set mixes a verb_noun convention (get_design_assessment, list_bot_issues, read_artifact_chunk) with bare noun tools (history, identity, impact, design, state, events, reviews, open), and the same concept is named both ways in places (get_development_state vs. development_state). Prefix families like studio_*, list_*, and get_* coexist without a clear rule. It is readable but clearly inconsistent.

    Tool Count1/5

    52 tools is well past the point where each one earns its place, and the set contains near-duplicate pairs that suggest consolidation rather than expansion. With 15+ tools carrying no real description, many entries feel like surface area rather than necessary capability.

    Completeness3/5

    Read coverage is broad across design, development state, reviews, evidence, artifacts, bots, teams, and onboarding, but the surface looks read-heavy: there are inbox/listing tools without an obvious send or post counterpart, and no clear create/update operations for designs, teams, or bots. Restore exists for artifacts but other write paths appear absent, which will force workarounds.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents and hosts to enforce deterministic repository boundaries via MCP, providing structured reads, supervised edits, snapshots, audits, and recovery with machine-readable evidence.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides coding agents with a durable, revision-aware project workspace for semantic context, governed source changes, verification, task checkpoints, and observability through an MCP interface.
      1
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to read a project's Git-backed kickoff, acceptance criteria, handoff package, progress, and next step, and to append validated, audited progress events as project records. It provides short-lived scoped credentials and fail-closed tool allowlisting for safe, resumable AI-assisted development.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to retrieve Git-backed project context, handoff packages, progress, and next steps, and to append validated progress events with matching project-record commits. This supports visible agent progress, resumable work, and safe handoffs while keeping high-risk actions outside the MCP surface.
      MIT