Story Crater Bot 35bef19e0c feat(agent-pod): persistent per-role agent pool, concurrency moves to repo level ...

coordinator.js now runs one long-lived planner/investigator/implementer/judge
session per repo (reused across every task via tmux send-keys) instead of a
fresh spawn per task per stage. Tasks within a repo run sequentially against
that pool; concurrency is now REPO_CONCURRENCY (default 3) concurrent repos
via a new --repos flag, not concurrent tasks in one repo's phase.

2026-08-18 21:30:49 -07:00

..

configmap.yaml

fix(agent-pod): remote tui session for multi-agent

2026-08-18 15:08:04 -07:00

console-ingress.yaml

fix(agent-pod): remote tui session for multi-agent

2026-08-18 15:08:04 -07:00

coordinator-configmap.yaml

feat(agent-pod): persistent per-role agent pool, concurrency moves to repo level

2026-08-18 21:30:49 -07:00

deployment.yaml

feat(agent-pod): persistent per-role agent pool, concurrency moves to repo level

2026-08-18 21:30:49 -07:00

hub-configmap.yaml

fix(agent-pod): remote tui session for multi-agent

2026-08-18 15:08:04 -07:00

hub-service.yaml

fix(agent-pod): remote tui session for multi-agent

2026-08-18 15:08:04 -07:00

kustomization.yaml

fix(api): retire Kong key-auth on model routes; agent-pod builds agent-manager fork + ships coordinator.js

2026-08-18 17:50:52 -07:00

pi-skills-configmap.yaml

feat(agent-pod): implementer and judge learn Playwright for UI verification

2026-08-18 18:37:46 -07:00

ssh-configmap.yaml

fix(agent-pod): remote tui session for multi-agent

2026-08-18 15:08:04 -07:00