Thanks for your interest in contributing. This guide covers everything you need to get started.
- Node.js >= 20
- Claude Code CLI installed and authenticated (required to run integration tests against a real workspace)
git clone https://github.com/arnavranjan005/cortex-harness.git
cd cortex-harness
npm installbin/ CLI entry point (cli.mjs)
src/ Core harness logic
commands/ CLI command handlers (init, run, resume, status, config)
engine/ Cycle runner, queue processor, scope enforcer
state/ Zod schemas for cycle-state JSON validation
templates/ Files scaffolded into user workspaces on `init`
agents/ Sub-agent role definition files
prompts/ Cycle prompt templates
scripts/ Runtime scripts copied to .harness/scripts/
tests/ Unit tests (Node built-in test runner)
npm testTests use Node's built-in node:test runner — no extra dependencies needed.
- Fork the repo and create a branch:
git checkout -b feat/your-feature - Make your changes
- Run
npm test— all tests must pass - Open a PR against
main
Check the Issues tab for open tasks. Issues labeled good first issue are scoped to be approachable without deep knowledge of the full engine.
- Keep PRs focused — one feature or fix per PR
- If you're adding a new command or changing CLI behavior, update
README.mdto match - If you're changing cycle state schemas in
src/state/, update the relevant Zod schemas and add a test
Open an issue with:
- What you ran (
cortex-harness run "..."or the exact command) - What you expected vs. what happened
- Your Node version (
node -v) and OS
By contributing, you agree your changes will be licensed under the MIT License.