openFTTH
FeaturesHow it worksDocsChangelogGitHub

Docs/Crew and tools

The crew

Four AI agents, the engines they can run on, and the steps that need your approval.

1 min read

The crew is four long-lived agents that design through the engine's own tools. They plan, explain and talk; the engine makes every engineering decision and records why. Nobody writes a number a tool has not returned.

Members

MemberRole
SurveyorReads the inputs: imports the data, runs the quality check and builds the street twin. Only the Surveyor imports.
PlannerRules and solve: places POP, FDHs and FATs, routes the cables, sizes them and assigns fibres.
CheckerValidates the design independently and reports violations with element ids.
DrafterExplains and delivers: the BOQ, the splice schedule and the GeoPackage.

Each member may call only its own engine tools. An engine tool that belongs to a teammate is refused with a pointer to hand it over, and the room stops a chain when a member repeats itself.

Choosing the AI engine

Pick the crew's engine in the composer's engine menu, which says what each option costs (free, free tier, subscription or paid):

  • Claude CLI or Codex CLI, with your own subscription.
  • OpenRouter or an OpenAI-compatible API, with your own key.
  • Ollama, a local model, free.
  • Hermes, an agent over ACP.

What the crew may not do

  • Shell and file tools are denied to every crew member. Local and API models only ever see the engine's tools.
  • While the crew works, manual editing is locked, so you and the crew never change the map at the same time.
  • The crew cannot sign off. Judging the inputs and signing the package are the engineer's job.

Approvals for risky tools

These steps never run without you. Each opens an approval card in the app:

ToolWhat it does
route_outside_ductsroute outside existing ducts
add_trenchdig a new trench
export_for_constructionexport the package for construction
rewind_designrewind the design to an earlier version
post_work_orderpost a work order to the network of record

Risky tools are never on a crew member's allow-list, and the engine itself refuses them without a valid approval from the card. Answer the card with allow or deny; the crew waits as long as the configured approval timeout (15 minutes).

Or no crew at all

Design automatically runs the same engine tools in stage order without any AI. It costs nothing and needs no account or key.