You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For LLM agents starting a session in a koru-driven repository:
agent-guide.md — full agent workflow guide
(ticket lifecycle, validation gates, anti-patterns, troubleshooting).
Start here if you are an LLM agent (Windsurf, Cursor, Claude Code).
planfile-llm-guide.md — ticket-driven
development with the planfile CLI. Covers ticket schema, labels,
priority, sprint workflow.
planfile-execution-gateway.md —
design for making planfile.yaml the execution gateway for shell, MCP,
API, human, and LLM actors.
cli-examples.md — practical Taskfile + CLI
examples for every common scenario (bootstrap, fix-alert, OpenRouter
lane, multi-repo refactor).
llm-tools/ — per-tool docs and install scripts
for every component in the koru pipeline.
semcod-ticket-sources.md — which semcod
analysis tools can generate Planfile tickets directly or through Koru
artifact adapters.
agent-backends-architecture.md —
layered map: plugin+socket, MCP, vendor CLIs, OS injectors (no single
universal “wake LLM” API).
ide-router.md — how koru chooses the active IDE
lane and keeps VS Code/VSCodium/Cursor/Windsurf/JetBrains/Zed separated.
ide-isolation.md (PL) — granice izolacji lane/socket,
dlaczego nie ma pełnego sandboxu między IDE i jak ustawić hardening,
żeby uniknąć cross-lane chat/event leakage.
autonomy-ide-cursor.md (PL) — autonomia
koru vs Cursor IDE: luka funkcjonalna i checklista wdrożeniowa.
photo-vql-jetbrains-wayland.md (PL) —
pętla vdisplay + koru photo-VQL (observe→decide→act→verify), skrypty
koru-drive-photo-vql.sh, guardy, PyCharm/Wayland — użyj tego do chat drive na pulpicie.
project-discovery-strategy.md —
how an idle planfile queue triggers whole-project code2llm discovery,
planfile ticket generation, and explicit IDE LLM status handoff.
../packages/coru/README.md — thin client
layer (coru) that keeps user-facing commands stable while koruenv + koru
internals can be refactored independently.
package-extraction-plan.md — practical,
incremental plan for moving selected modules from src to packages/*.
For human operators / DevOps:
../README.md — top-level project description and
architecture overview.
This split is what makes koru economically viable for daily development:
the heavy lifting happens in your IDE LLM (already a sunk cost), while
the OpenRouter lane is reserved for things that genuinely benefit from
out-of-band, automated, headless processing.
# Entry point — pick the highest-priority ticket
task tickets:next
# Read ticket details
planfile ticket show PLF-XXX
# Edit code (your IDE's LLM does the work)# ...# Validate locally (no LLM API calls)
task quality:regix:local
task test
task monitor:probe
# Commit (pre-commit hooks do final validation)
git commit
# Mark done
task tickets:done -- PLF-XXX
Caveats
The default ticket-driven path is more stable than the opt-in
OpenRouter automation lane. If task quality:improve or
task monitor:test-heal fails but redsl improve <path> works locally,
treat it as an infrastructure problem (compose / webhook wiring), not a
product bug.
Configuration in templates/ is from a real production deployment
(maskservice/c2004). Adjust redup.tomlmax_groups / max_lines to
your project size before adopting blindly.
Full catalog (docs/*)
Complete index of documentation in this directory. Start with
README.md for the project overview and
CHANGELOG.md for release notes.