Skip to content

AGENTS.md

Latest commit

 

History

History
68 lines (47 loc) · 3.13 KB

AGENTS.md

File metadata and controls

68 lines (47 loc) · 3.13 KB
Raw

Case — Agent Harness

Spine repo for orchestrating agent work across WorkOS open source projects. Humans steer. Agents execute. When agents struggle, fix the harness.

First Step

Run the session command to gather context before doing anything else:

SESSION=$(ca session <target-repo-path> --task <task.json>)
echo "$SESSION"

Projects

Repo Path Purpose Stack
cli ../cli/main WorkOS CLI — AuthKit installers, resource management TS/pnpm
skills ../skills WorkOS integration skills TS/pnpm
authkit-session ../authkit-session Framework-agnostic session management TS/pnpm
authkit-tanstack-start ../authkit-tanstack-start AuthKit TanStack Start SDK TS/pnpm
authkit-nextjs ../authkit-nextjs AuthKit Next.js SDK TS/pnpm
workos-node ../workos-node/main WorkOS Node.js SDK TS/npm

Full metadata (commands, remotes, evidence strategy): ~/.config/case/projects.json

Navigation

Topic Location
Architecture patterns docs/architecture/
Shared conventions docs/conventions/
Golden principles docs/golden-principles.md
Failure matrix docs/failure-matrix.md
Playbooks docs/playbooks/
Agent roles agents/
Entropy management docs/conventions/entropy-management.md
Repo learnings Target repo .case/learnings.md

Task Dispatch

Tasks are markdown files that agents execute. Runtime task files live in the target repo's ignored .case/tasks/active/.

  • Format spec: tasks/README.md
  • Templates: tasks/templates/

Pipeline: scout → implementer → verifier → reviewer → closer → (retrospective)

Onboarding agent (out of the pipeline): interviewer — invoked by ca onboard --interview to capture evidence strategy rationale, verification notes, and repo learnings.

Lifecycle: .case/tasks/active/ → PR opened/merged status in the task JSON

Working in a Target Repo

  1. Run ca session {repo-path} --task {task-json} to gather context
  2. Read the repo's CLAUDE.md (or CLAUDE.local.md) for project-specific instructions
  3. Run ca bootstrap {repo-name} to verify readiness
  4. Follow the repo's PR checklist before opening a PR
  5. Run ca check --repo {repo-name} to verify conventions

Maintenance

  • Convention checks: ca check — enforce shared rules

Improving This Harness

See CLAUDE.md for how to maintain and improve case itself.