Single-maintainer reality check: where Bernstein needs help (April 2026)

[chernistry]

Where Bernstein is, what's lagging, what would actually help.

Bernstein is fine. Stars are fine, downloads are fine, the codebase ships. The gap is between what's shipped and what's documented, tested, or triaged. That gap is widening because most of the work is one person.

External contributors have landed PRs: @oldschoola, @0xbboyd, @alexanderxfgl-bit, @TheCodingDragon0, @vedangit, plus the rest of the contributors graph. Architecture, the 37 adapters, the release pipeline, docs, triage are still mostly me.

Quick state of the codebase:

• 22 sub-packages under src/bernstein/core/ (orchestration, agents, tasks, quality, cost, security, planning, routing, observability, protocols, persistence)
• 37 CLI adapters (Claude Code, Codex, Gemini CLI, OpenHands, Aider, Cursor, Goose, Qwen, Cloudflare Agents, OpenAI Agents SDK, others)
• 964 tests (unit, integration, e2e)
• MCP server mode (stdio, HTTP/SSE). A2A protocol. Cloudflare Workers tier. S3/GCS/Azure/R2 artifact sinks
• ~250 GitHub stars since the repo moved to its current org. Cited as prior art by Overcode, NOVA Cognition Framework, nibzard's pattern library. In 15+ awesome-lists

What's behind:

• Docs. mkdocs site exists but is partial. Adapter docs and architecture pages drift behind code.
• Tests. v1.9 shipped ten features. Coverage on the ACP server and autofix flow is uneven.
• Triage. Some PRs sit too long. Bug reports without repros sit longer.
• Adapter parity. Not all 37 adapters honour the current lifecycle hook contract.
• Examples. bernstein init works, but a real examples/ dir with 3–4 plan files would help onboarding.

If you want to help, in rough order of leverage:

1. Docs PRs. Pick any adapter under src/bernstein/adapters/, write a one-page user doc. I'll merge same day.
2. The 15 feature tickets opened recently (feat: lazy tool search to keep MCP tool descriptions out of context #973–feat: synthesise reusable patterns from task transcripts into prompt updates and skills #987), sourced from nibzard/awesome-agentic-patterns. Each has scope, file paths, an LOC estimate.
3. Triage. Ask for repros on stale issues, close obvious dupes. Keeps the project breathable.
4. Adapter parity sweep. Pick one adapter, run it through current lifecycle hooks, PR the drift.
5. Examples. Real plan files running on real repos.

Apache-2.0, no CLA, no copyright assignment. PRs reviewed same week, usually same day if scope is clear.

Not asking for money. GitHub Sponsors exists if anyone insists, but that's not the point here. Not closing the project. Not moving licenses. The ask is time and attention.

If any of the above lights up for you, comment or open a draft PR.

— Alex