Architecture
Agent task executor adapter
Agent task executor adapters are the boundary between Homeboy core and the systems that actually run agent work. Core owns...
Runner contract
The contract between Homeboy core and runner scripts: what capabilities exist, what env vars flow in, what sidecar files scripts...
Keychain and Secrets Management
Homeboy securely stores sensitive credentials using OS-native keychain/credential manager systems. Overview Homeboy never stores secrets in plaintext configuration files. All...
JSON output contract
Homeboy prints JSON to stdout for most commands. Exceptions: homeboy self docs prints raw markdown (or newline-delimited topic names for...
Release Pipeline System
Homeboy release automation is a local-first planner/executor for component releases. It turns component metadata, conventional commits, extension release actions, and...
CI result JSON contract
Homeboy CI results are exposed through the existing global --output <path> flag. The flag writes the same JSON envelope Homeboy...
API Client System
The API client provides HTTP request capabilities with template-based authentication per project. Overview Homeboy projects can configure an API client...
Embedded docs: topic resolution and keys
Homeboy embeds markdown files from docs/ into the CLI binary at build time. In addition, homeboy self docs reads documentation...
Agent Runtime Contract Handshake
Homeboy owns the generic protocol for agent runtime handoff. Extensions own the runtime-specific facts that populate that protocol. Core records...
Artifact Postprocess Runner Contract
Homeboy core owns a product-neutral artifact postprocess contract for persisted artifact roots. The contract schema is homeboy/artifact-postprocess/v1. A plan declares:...
Execution Context
Execution context is the environment Homeboy passes to extension runners and extension-backed pipeline steps. Overview When Homeboy executes an extension,...
Provider fanout boundary
Homeboy core owns durable orchestration and provider-neutral evidence. Runtime providers own backend-specific execution details. The seam is the AgentTaskRequest/AgentTaskOutcome adapter...