Connecting your tools to Gantry

What are we connecting?

We are connecting the tools your project already uses—from code and team documents to mechanical and electrical design. A customer’s agent can use a local Gantry CLI to prepare a change, update an allowed target, and bring the result back into the development record.

The aim is to keep work in the tools that already hold it, while keeping the reasons and results connected in Gantry. These are limited update operations, not full editors or continuous synchronization.

How does an update become part of the record?

1. Prepare. Read the current target and save the proposed change, its reason, and the version it is based on.
2. Apply. With authority for that target, apply the exact reviewed plan. Preparing a plan does not grant permission to execute it.
3. Check. Read the result back. If the outcome is uncertain, inspect it before sending another update.
4. Record. Export the before-and-after evidence and publish it into an authorized Gantry development state.

Recording the result does not automatically adopt a design, start a review, or prove that requirements have been met.

What if someone else changes the same item?

Some operations use a file hash, commit, page version, ETag, or workspace revision to guard against conflicting updates.

Others can only check before writing. Another person or agent can still change the item between that check and the update. Those operations are blocked by default unless non-atomic execution is explicitly allowed. This allowance does not remove the race; exclusive editing or coordination with the service owner is still needed.

Desktop updates also need exclusive editor access: other agents and GUI editing must pause during the operation. A local journal records attempts, but cannot lock out other applications or machines. There is no single transaction spanning these tools.

Where does the agent run?

The agent runs in your environment, using your tool accounts and permissions. Gantry does not host the agent or supply vendor licenses or model usage for this path. Vendor quotas and runtime costs still apply.

Credentials stay in private environment references. Captured evidence can contain private project content and belongs only in authorized storage and Gantry states.

What stays outside this update?

This work does not add full two-way synchronization, webhook sync, or OAuth installation and refresh. File updates do not create branches, files, pull requests, merges, or deletions. Export-only integrations remain export-only.

The desktop connectors do not create whole designs or cover every vendor API. Altium and Allegro generate scripts for an operator to run; they do not automate host execution or verify a saved file. For CAD, reading back a value does not prove strength, electrical behavior, manufacturability, or physical performance.

Why this matters for Gantry

A decision can change code, a design parameter, a table, and a team’s notes. Our direction is to connect those actions to the same development context, so the next agent can see what changed and what was actually observed.

Development status

These additions are experimental, unreleased implementation work. Tests use simulated service responses and synthetic application APIs. Live service accounts and licensed desktop applications have not been tested.

Each desktop path needs qualification with its exact application and SDK on a disposable project before agents are allowed to write. A value read back from an application is not physical validation or production qualification.