🦀 Gajae Code

Documentation

Harness

Use the Gajae Code harness to run coding-agent sessions with observable lifecycle, submit gates, and workspace-aware control.

Why a harness?

A coding model is useful only when it can be steered, observed, paused, and verified. The harness turns an agent run into a managed session with lifecycle state, owner liveness, branch context, and submission gates.

Design intent: do not rely on a terminal screenshot or a half-remembered prompt. Track whether the owner is live, whether the session is ready for input, and which workspace/branch the work belongs to.

Typical loop

gjc
/skill:deep-interview
/skill:ralplan
gjc ultragoal "implement, verify, and report evidence"

The exact commands depend on the task, but the pattern stays the same: make the task explicit, let the agent work in context, then require validation and a terminal verdict.

Operational guardrails

  • Use dedicated worktrees for risky implementation and review work.
  • Keep branch metadata aligned with the actual checkout.
  • Submit follow-up prompts only after the session is observable and ready.
  • Retire completed sessions instead of leaving stale panes behind.