Thanks for contributing.
Understand your change. If you can’t explain what your code does, why it belongs in AgentV, and how it affects existing behavior, don’t submit it yet.
Using AI tools is fine. Shipping code you don’t understand is not.
For non-trivial features or behavior changes, open an issue first and wait for maintainer alignment.
AgentV is early-stage, so we prioritize:
- clear problem statements
- small focused PRs
- changes that keep core minimal and push niche behavior to plugins
bun install
bun run build
bun testRun CLI changes from source during development:
bun apps/cli/src/cli.ts --helpAlso ensure:
- PR explains what changed and why
- tests/docs are updated when relevant
- no unrelated refactors in the same PR
- pre-push hooks pass (
build,typecheck,lint,testrun automatically on push)
- Branch from
main - Open a PR (draft is fine)
- Keep iteration scoped and reviewable
If your change affects eval behavior or output shape, include an example command and result snippet in the PR description.