Six tools for agents that do real work. Use one, or several.And a cloud, built slowly around them.

Six tools, each named for something you pass on a hill walk.

None needs the others, and none needs a particular agent: they ship as CLIs and skills, so the agents you already run can use them. Bothy is different in kind: one specific use, a small harness for leaving an agent on a client's machine. So is Drove: it runs the agents themselves, a planner and its workers in herdr panes.

• Quarry

  Pipeline

  The CRM where agents claim a lead, work it, and release it with an outcome.

  quarry.montytorr.com

• Cairn

  Memory

  The memory and task board your agents share with your people: read before they start, written to as they work. A Lab, switched on per instance, holds the ideas that are not work yet.

  cairn.montytorr.comSource

• Holloway

  Contracts

  Signed, turn-limited contracts, so an agent you do not control can do real work for you.

  holloway-cloud.montytorr.comSource

• Bothy

  On site

  One specific use: a small harness for leaving an agent on a client's machine, woken by signed webhooks, cron, chat or polling.

  bothy.montytorr.comSource

• Trig

  Map

  Your agents understand how your company works: its processes, people and numbers, each grounded in the systems that run them.

  trigcloud.montytorr.com

• Drove

  Crew

  One planner and several coding agents side by side in herdr panes, each worker in its own git worktree with one Cairn task. You choose the planner, Claude Code or Codex; the workers are Claude Code or Codex too. No daemon.

  drove.montytorr.com

Six problems, six tools.Each drawing is one on its own.

Every panel stands alone: the product's real mechanic, drawn small, and what it gives you. Pick the one whose problem you have.

• QuarryPipeline

  Two agents must never call the same lead.

  Agents claim a lead under a 30-minute lease. When three reach LEAD-318 at once, one wins and the other two get exit 9: go and find other work, do not wait. A call ends in a release with a disposition, an outcome and a --next time, and the lead stays out of the pool until then.

  What it gives you

  A pipeline your agents work without ever calling a lead twice or dropping one.

  Works alone. Pairs well with Cairn: the same claim-and-release habit; your agent can carry a won lead into a Cairn task. A shared idea, not an integration.

• CairnMemory

  An agent should not start from zero.

  When a session opens, Cairn's hook prints what this agent holds, where the last session left off, and what is already known here. Findings go on tasks as notes, and the ones worth keeping become knowledge that every later session is briefed with. People work the same board: every task has a person who owns it, separate from the agent claiming it right now. Switch the Lab on and the same instance holds what is not work yet. An idea or a technology to evaluate becomes a subject that moves through stages you curate, with a write-up, a log, notes and files, and it cannot close without a conclusion. Its todos are ordinary Cairn tasks. A lab you share is simply another Cairn instance, and work leaves one by hand-off to another instance or to GitHub, with sync reading the outcome back.

  What it gives you

  Agents that pick up where the last session stopped, on a board your people work too, and a Lab where every dead end is written down.

  Works alone. Pairs well with Trig: Trig reads Cairn's knowledge and task activity, and Cairn's briefing carries a line from Trig's map.

  ## Cairn [ACME]
  You are holding:
    ACME-12  doing  Import the seat list
  Last session here left off:
    3 rows fail on accented names
  Known here (cairn know <slug>):
    csv-exports-are-latin-1
  Lab: 4 to explore · 1 exploring
    LAB-12  exploring  pgvector -- 2 todos
  Trig: the map of what exists (scanned 3h ago)
  

• HollowayContracts

  Real work from an agent you do not control.

  A contract sets the terms, and every turn is signed. It says how many turns there can be: when the budget is spent, no further turn can be taken. A person can step in through the operator channel without holding the signing key, and the contract closes with an outcome.

  What it gives you

  Work from agents you do not control, on terms both sides signed and can audit.

  Works alone. Pairs well with Cairn: Holloway's reactor closes the Cairn task labelled a2a-contract:<id> when that contract is accepted.

• BothyOn site

  An agent that has to live on a client's machine.

  Some work cannot leave the building. Bothy is a small harness you leave there, woken by a signed webhook, cron, chat or polling. The event is fsynced before the 202 goes back. The admission gate checks the lane, a free slot and the budget; Codex runs under supervision; its process group is killed, and only then is the outcome written to the audit chain.

  What it gives you

  An agent that works where the data has to stay, and records how every run ended.

  Works alone. Pairs well with Cairn: a run started with --ref is claimed, noted and released in Cairn. A plain webhook wake does not write to Cairn.

• TrigMap

  Your agents know the code, not how the company works.

  Trig gives your agents the business: its lifecycles and processes, its people and its numbers, each grounded in the code, data and infrastructure that run them. Connectors survey what you run, and your agent writes how the business works on top. Ask how a customer goes from signed to live, who owns billing, or what runs by itself, and the answer points at the file behind it.

  What it gives you

  Agents that answer questions about the business, with the file behind each answer.

  Works alone. Pairs well with Cairn: with its Cairn connector configured, each scan reads Cairn one way: knowledge comes in as contributed facts, task counts as observed ones.

• DroveCrew

  Several agents on one codebase, without treading on each other.

  Drove runs one planner and several workers side by side in herdr panes. You choose the planner, Claude Code or Codex, and start it one of three ways: /orchestrate in Claude Code with the mod, drove plan --kind claude without it, or drove plan --kind codex. The workers are Claude Code or Codex under any planner. Each worker has its own git worktree and one Cairn task, and reports done, question or blocked. The planner reads the diff, sends approve or changes, and merges only what passes the repo's checks. Workers never push, the planner never edits code, and there is no daemon: the run is plain files.

  What it gives you

  Several agents working at once, each on its own branch, with one place that reviews and merges.

  Works alone. Pairs well with Cairn: every worker is spawned with one Cairn ref, and its brief has it claim that task before anything else.

Most start with one. Some pairs earn their keep.

These are the joins that exist, each drawn with its honest line: solid where code in one product talks to the other, dashed where two share a habit and no code.

• Cairn + Trig

  The strongest pair. Trig reads Cairn's knowledge and task activity, one way; Cairn's session briefing carries a line from Trig's map.

• Holloway + Cairn

  When a contract is accepted, Holloway's reactor closes the Cairn task labelled a2a-contract:<id>.

• Bothy + Cairn

  A run started with --ref is claimed, noted and released in Cairn. Without a task ref, nothing is written there.

• Drove + Cairn

  Drove spawns each worker with exactly one Cairn ref, and the worker's brief has it claim that task before anything else. Cairn is the queue: Drove keeps none of its own.

• Quarry + Cairn

  The same lease habit: claim, keep it alive, release with an outcome. Your agent carries a won lead into a task; no code joins them.

Separate tools, a few good joins.

The reference picture. Your agents reach each tool through its CLI and skill, and none of the tools needs another. Solid lines are code that ships, dotted means compatible through a standard, dashed means the same idea with no code.

1. 1

   Your agentsCairn, Trig, Holloway, Quarryshipped

   OpenClaw, Claude Code, Codex and Hermes use Cairn, Trig, Holloway and Quarry through each product's CLI and skill. No product needs a particular agent, or the others.

2. 2

   CairnTrigshipped

   Trig reads Cairn through its connector, one way: knowledge becomes contributed facts, task counts observed ones.

3. 3

   TrigCairnshipped

   Cairn's session briefing carries one line from Trig: when the map was last scanned, and how to ask it.

4. 4

   BothyCairnshipped

   When a run carries a task ref (bothy run --ref, or the agent's bothy_note tool), Bothy records it in Cairn: claim, note, release. A plain webhook wake does not.

5. 5

   HollowayBothyshipped

   Bothy carries Holloway's reactor code, and closes the Cairn task labelled a2a-contract:<id> when that contract ends.

6. 6

   HollowayBothycompatible

   Any signed webhook can wake Bothy, Holloway's included. Bothy checks the signature, not the sender.

7. 7

   QuarryCairnthe same idea, not an integration

   Quarry's 30-minute lease on a lead has the same shape as Cairn's 15-minute claim on a task: claim it, beat to keep it, and anyone may take it over once it goes quiet.

8. 8

   DroveCairnshipped

   drove spawn takes one Cairn ref per worker and puts it in the worker's brief, whose role text has it claim that task with Cairn's CLI before anything else. Drove keeps no queue of its own.

One product at a time,and only where it earns its place.

There is no platform to sign up for. Each product gets a hosted side when there is something for it to do that one install cannot, and it is different for each. For Bothy the answer is nothing, on purpose, and Drove has none: it runs in your own herdr panes.