Thanks for checking out GhostCode. This project is a small, forkable harness template—contributions that keep it understandable are especially welcome.
Look for issues labeled good first issue (create the label on GitHub if the filter is empty):
- https://github.com/amitmishrg/ghostcode/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
Starter tasks if none exist yet:
- Add a local tool (with schema in
@ghostcode/shared+ executor inlocal-tools.ts) - Add or tweak a theme in
packages/cli/src/theme.ts - Improve docs in
docs/BUILD-YOUR-OWN-HARNESS.md - Fix install / Bun / Windows path issues
bun install
export ANTHROPIC_API_KEY=... # and/or OPENAI_API_KEY
bun run dev:cliLink globally:
bun run link:cli
ghostcode| Path | Purpose |
|---|---|
packages/shared/ |
Tool schemas, modes, system prompt, models |
packages/cli/ |
TUI, transport, local tools, sessions |
docs/ |
Deep-dive docs for forkers |
See docs/BUILD-YOUR-OWN-HARNESS.md before large refactors.
- Keep PRs focused—one tool or one doc section per PR when possible
- Match existing style (TypeScript, minimal comments)
- Test manually:
bun run dev:cli, run PLAN and BUILD turns in a real repo
You do not need permission to fork and rename GhostCode (MIT). If you publish a derivative, keep the license file and consider linking back to this repo.
When opening issues, include:
- OS, Bun version (
bun --version) - Install path (
npm -gvs clone vsbun link) - What you expected vs what happened
Feature requests for MCP, sub-agents, or workflow gates are fine—label them enhancement so we can prioritize from real demand.