Help improve any part of Spark.
Use this page when a doc is confusing, a module behaves oddly, an installer step could be safer, or your agent found a real improvement. Feedback should be easy for humans and precise enough for agents to route into the right repo.
Choose the repo first.
Pick the area that best matches what you saw. If you are not sure, use Site and docs; an agent or maintainer can reroute the report.
Site and docs
Spark-Agent-SiteInstall page, docs, legal pages, LLM indexes, hosted installer metadata.
CLI and installer
spark-cliSetup, dry-runs, provider selection, autostart, healthchecks, logs, update commands.
Research and autoloops
spark-researcherResearcher commands, evidence packets, OTOLO/autoloop runs, chip authoring, ledgers.
Runtime routing
spark-intelligence-builderAgent and Mission provider routing, memory bridge, runtime role behavior.
Memory chip
spark-domain-chip-labsMemory packets, long-term memory evaluation, benchmark promotion rules.
Telegram chat
spark-telegram-botBot commands, message handling, Telegram diagnostics, long polling behavior.
Mission Control
vibeship-spawner-uiSpawner UI, Kanban, Canvas, project boards, mission visibility.
Character and permissions
spark-characterRole, voice, permission awareness, persona boundaries.
Not sure where it belongs?
Start with Site and docs. Describe the module or command you touched, and we can move the feedback to the right Spark repo.
Ask an agent to prepare it.
Turn observations into a useful report.
Do not just say "this is broken." Include the repo, page or command, expected behavior, actual behavior, reproduction steps, safe logs, and the smallest suggested improvement.
Opening a repo link sends you to GitHub. Sign in there, then create the issue or PR with secrets removed.
Repo: <target repo> Area: <docs | installer | provider | module | benchmark> Expected: <what should have happened> Actual: <what happened instead> Evidence: <redacted command, screenshot, or link> Suggested fix: <smallest useful change> GitHub route: <issue or PR, after user approval>
What high-signal feedback looks like.
Good feedback gives a maintainer or agent enough signal to act without guessing. It is specific, private by default, and small enough to turn into a check or PR.
Clear
Point at the exact page, command, module, or repo.
Safe
Remove keys, tokens, private memory, names, and raw logs.
Useful
Name the smallest change, screenshot, command, or test.
Provider setup docs make split roles unclear
- Surface
/docs/providers/, setup copy- Expected
- Agent and Mission defaults are easy to choose.
- Actual
- The split-provider path feels hidden.
- Evidence
- Redacted screenshot or exact paragraph.
- Smallest fix
- Add one sentence and one setup check.
Redacted: no provider keys, Telegram tokens, private memory, or private repo text.
Open source appreciation
Useful issues, redacted reproductions, and PRs make Spark easier for everyone. When practical, we will acknowledge helpful contributors in issues, release notes, or docs updates.