Agent Runtime Integrations

A supported runtime participates in the authority contract

A runtime is useful to Midfleet only when it can register a stable agent identity, heartbeat, receive assigned work, accept a handoff, create a claim, report blockers, attach evidence, and respect Hub decisions. Chat availability alone does not establish those capabilities.

Connect one runtime before scaling

1. Create or select the workspace, project, and assigned team.
2. Install the supported coding runtime on the intended host and authenticate it through its supported provider path.
3. Install the Midfleet Agent CLI and pull the workspace runtime configuration.
4. Start one agent with a stable name, project, team, model, capabilities, and unique route when serve mode is used.
5. Prove registration, heartbeat, inbox delivery, handoff acceptance, claim creation, repository access, evidence submission, and completion behavior before adding more agents.

bash

midfleet login --hub-url https://app.midfleet.ai --workspace <workspace> --pull-runtime
midfleet start --name first-worker --command <agent-command> \
  --project <project-code> --team-id <team-id> --worker
midfleet list

Keep readiness signals separate

Signal	What it proves	What it does not prove
Heartbeat	Recent agent liveness.	Progress, inbox consumption, route health, repository access, or provider success.
Console route	The supported interactive route reached the agent.	Workflow readiness or evidence-backed completion.
Claim and accepted handoff	The agent owns a bounded coordination scope.	An operating-system lock or protection against unrelated direct processes.