Core workflows

Choose How You Want To Work

Start with the communication mode, then follow the generated workflow to manifest-backed commands. The command list is the reference layer, not the first thing a new user has to decode.

Version 1.1.0 · Manifest a6ee797254ff

Separation

Executor Is Replaceable; Repository Governance Persists

Codex, Claude, hosted models, local models, or humans may execute work where their environment allows it. The repository keeps the durable state, command manifest, gates, evidence and handoff boundary.

primary web-LLM path

File Transfer

The human and the LLM exchange bounded Kit transfer files while the repository remains the source of truth.

Best for: Web or hosted LLMs without direct terminal or repository access.

agentic-kit transfer read-user-taskRun agentic-kit transfer read-user-task.primitive · BOUNDED
agentic-kit transfer submit-user-taskRun agentic-kit transfer submit-user-task.primitive · BOUNDED
agentic-kit transfer remote-nextRun the next repo-backed transfer order for local or remote work handoff.orchestrator · BOUNDED
agentic-kit transfer chat-switch-completeCreate a deterministic successor handoff package and prompt projections.orchestrator · BOUNDED

manual fallback

Copy and Paste

The LLM proposes a bounded terminal block, the human runs it, and the important output is returned to the conversation.

Best for: Small manual web-LLM sessions where a file-transfer carrier is not needed.

agentic-kit workflow requestRequest the configured declarative workflow without running it.primitive · BOUNDED
agentic-kit workflow runRun the current workflow, or set a stored workflow item and run it.primitive · BOUNDED
agentic-kit transfer log-headerRender the dynamic local-to-LLM copy/paste log header from rule files.primitive · BOUNDED
agentic-kit transfer chat-switch-completeCreate a deterministic successor handoff package and prompt projections.orchestrator · BOUNDED

executor-controlled workspace path

Agent Direct

The executor can run Kit commands directly, but repository governance, evidence, safety classes and handoff state remain separate from the agent.

Best for: Executors with controlled repository and terminal access.

agentic-kit command-forSelect the deterministic wrapper command for a raw command or task tag.diagnostic · READ_ONLY
agentic-kit transfer remote-work-startPrepare a remote work branch with freshness, status, and transfer safety checks.orchestrator · BOUNDED
agentic-kit transfer pr-create-completeCreate, validate, merge, and optionally close out a PR without manual PR/SHA copying.orchestrator · BOUNDED
agentic-kit transfer protected-diff-planWrite the current diff to the OS temp directory and run the Python protected change planner on it.diagnostic · READ_ONLY
agentic-kit transfer chat-switch-completeCreate a deterministic successor handoff package and prompt projections.orchestrator · BOUNDED

experimental early surface

GUI

The GUI entry point is available, but full parity with every CLI command is not claimed. The manifest remains the command authority.

Best for: Local operator visibility over manifest-backed actions and readiness checks.

agentic-kit gui-readiness-gateRun the pre-GUI readiness gate.diagnostic · BOUNDED
agentic-kit cockpit runRun agentic-kit cockpit run.primitive · BOUNDED
agentic-kit cockpit selectRun agentic-kit cockpit select.primitive · BOUNDED

Minimal cycle

Task To Handoff

Select the interaction modeChoose File Transfer, Copy and Paste, Agent Direct, or the experimental GUI surface.
Inspect before mutationUse read-only or dry-run commands where available and keep target-owned decisions explicit.
Run a bounded sliceMake one coherent change on a branch, record gates and evidence, and keep PR review visible.
Close the handoffGenerate the successor package so another session or executor can continue from repository state.

Why not only Git, CI and AGENTS.md?

The Kit complements Git and CI; it does not replace them. Git records history, GitHub coordinates PRs, CI validates configured checks, and AGENTS.md guides an executor. The Kit keeps long-lived operational state, governance, evidence, command metadata and handoffs in the repository.

Boundaries

What Persists

Git records history and diffs; the Kit adds machine-readable operational state and handoff contracts.
GitHub PRs coordinate review; the Kit wraps PR lifecycle checks when evidence is available.
CI validates configured checks; the Kit records when remote target-CI is absent or not claimed.
AGENTS.md guides an executor; the Kit keeps durable governance, evidence and command metadata in the repository.
The executor is replaceable; repository governance persists.
The Kit itself makes no LLM API calls and does not require an LLM API; executor services may have their own costs.
YAML and JSON state are versioned, diffable and reviewable, but they create file volume and projection-refresh work.

State format

Why YAML And JSON

Repository state is versioned, diffable, reviewable, and portable between sessions, machines and executors. The tradeoff is more files and explicit projection refresh work instead of an invisible state service.

Evidence-bound Brownfield result

B1 Closeout

The historical B1 threshold window provides evidence beyond self-hosting, but one familiar repository is not enough to establish general Brownfield portability.

Status B1_EVALUABLE · Source docs/reports/POST_V1_0_5_B1_EVIDENCE_CLOSEOUT_20260826.json · Rule-Ack evidence released_package_targeted_external_retest

Measured Facts

StatusB1_EVALUABLE
Real cycles5
Merge-boundary cycles4
Administrative refresh PRs6
Legacy seams72 to 58
Full-suite runs1483 to 1490 tests
Cycle 005Cycle 005 changed CI configuration rather than functional code, so it has no historical local full-suite entry.
Core defects found4

Limits

The Brownfield repository was familiar and private, not an independent public adopter.
Cycle 005 changed CI configuration and has no historical local full-suite entry.
The external merge wrapper still has a local non-return defect after successful remote merge.
Fixes on Kit main and fixes in a released package are separate evidence types.