GitTrove.com
Independent agents. Connected work.

Your agents work in parallel.Your software still works together.

Give each package an agent. Approve what it should do.
See whether the changes work together in your application before you release them.

Spend less time relaying instructions, untangling dependencies
and reviewing changes that were never ready.

Watch the workflow
Stead / Improve session handling
ILLUSTRATIVE WORKFLOW
Coordinating session handling for SteadAssignments approved
AirKernelAgentOwns AirKernel
Working

Expose the session lifecycle hook.

Prompt v3 · approvedScoped workspace
AirGuardAgentOwns AirGuard
Working

Keep session renewal compatible.

Prompt v2 · approvedScoped workspace
Stead application check

Candidate packages tested separately and together

↳ Compatibility gate
Versioned packages, explicit collaboration.You approve the decisions.
AirKernelAirGuardAirD1LocalCIAirAdmin
One owner per packageApproved assignmentsApplication evidence
Less coordination. More confidence.

More agents should mean
less work for you.

You give an agent a task. It changes a dependency. Another agent works around that change. Both report success. Now two projects only work with each other’s unfinished branches, and you’re the one sorting it out.

GitTrove makes those dependencies visible while the work is happening.

01 / OWNERSHIP

One package.
One accountable agent.

AirKernel, AirGuard, AirD1, LocalCI and AirAdmin each have an accountable agent. Each gets a clear assignment, scoped access and its own workspace.

They work concurrently and collaborate through explicit requests and versioned packages.

AirKernelAirKernelAgent
One owner
AirGuardAirGuardAgent
One owner
AirD1AirD1Agent
One owner
LocalCILocalCIAgent
One owner
AirAdminAirAdminAgent
One owner

Separate workspaces. Explicit requests. Versioned releases.

PROMPT / v3Approved

Expose the session lifecycle hook

Outcome
AirGuard can renew a session before the response is sent.
Scope
AirKernel lifecycle API and regression tests.
Evidence
Passing package tests and a Stead session renewal check.
✓ Exact version approvedHuman decision
02 / ASSIGNMENT

You approve the assignment
before the work begins.

Read a short Prompt: the outcome, the scope and the evidence you expect. Edit it until it’s right. Approve that exact version.

When an agent needs another package changed, it brings you a proposed assignment for that package’s owner.

03 / COMPATIBILITY

Catch the break
between the packages.

A package can pass its own tests and still break your application.

GitTrove tests candidate releases separately and together against the application that uses them. When something fails, you see the expected behavior, the actual result and the test that reproduces it.

Stead / candidate check3 checks
AirKernel package tests✓ PASS
AirGuard package tests✓ PASS
Session renewal in Stead! FAIL
test_session_renewalExpected   Session cookie renewed
Actual    Response already sent
Repair assignment proposedReview required ↗

Session handling / outcome evidence

Approved assignmentsPrompt v3 + Prompt v2
Versions testedkernel candidate.2
guard candidate.3
Application checksPassed together
Needs your decisionRelease candidates
✓ Evidence checked against the latest changes
04 / REVIEW

Review an outcome
you can understand.

Follow one improvement from approved Prompts to package changes to application checks. See the exact versions tested, what passed, what remains uncertain and what needs your decision.

When the code changes, its evidence gets checked again.

Built for the work behind Stead.

Stead is our proving ground: a real application built on independently released packages. The goal is straightforward. Agents should help us ship better software without turning separate projects into one tangled codebase.

SteadREAL APPLICATION. REAL DEPENDENCIES.
Follow one improvement

See the whole workflow.

Two package agents work at once. A compatibility check catches a broken assumption. A human approves the repair. The corrected packages are tested in the application.

SESSION HANDLING / INTERACTIVE WALKTHROUGHILLUSTRATIVE DEMO
01 / ASSIGN

Approve the work

Two clear Prompts. Two package owners.

02 / BUILD

Work in parallel

Independent changes. Versioned candidates.

03 / CHECK

Find the break

Package tests pass. The application catches a mismatch.

04 / REPAIR

Verify together

You approve the repair. The application checks pass.

Start with an approved assignment. AirKernelAgent and AirGuardAgent each receive a scoped Prompt. You approve the exact versions before either agent begins.

Step 1 of 4 · Advance at your own pace

Separate packages. Shared confidence.

That’s the demo GitTrove needs to earn your trust.

Watch the workflow
Explore the source

The packages behind the workflow.

The packages and tools behind the workflow have separate repositories. Repository access may require permission.

AirKernel ↗AirGuard ↗AirD1 ↗LocalCI ↗

AirAdmin is included in the workflow. Its repository link is not available here yet.
Try the workflow

Start with the tools
available today.

The agent workflow above is an illustrative walkthrough. Self-service agent assignments and application compatibility checks are being developed.

LocalCI

Run your project's existing checks in your own environment, keep the output in your terminal, and optionally report the verdict to GitHub as a commit status. Your source stays in your repository.

29 USDC every 30 days · Explore the package → AirSuite

Air improved and optimized for Cloudflare Workers and D1. Includes AirKernel, AirD1, and AirGuard for Python web applications, persistence, and authentication.

99 USDC every 30 days · Explore the package →

Package subscriptions include the listed tools and available updates. They do not include the agent coordination workflow shown here. Review each listing and the terms of service before subscribing.