[limen FORCE-route-all-services] Router fans across ALL paid services, not just the 6 vendors#41
[limen FORCE-route-all-services] Router fans across ALL paid services, not just the 6 vendors#414444J99 wants to merge 1 commit into
Conversation
limen task FORCE-route-all-services
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c3fdd5b86a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| total += dispatch_tasks( | ||
| limen, | ||
| tasks_path, | ||
| agent=paid_agent, | ||
| budget=budget, | ||
| dry_run=dry_run, |
There was a problem hiding this comment.
When limen dispatch --agent fleet --live is run against an unrouted board with a target_agent: any task, this loop hands that task to the first reachable paid lane in PAID_AGENT_ORDER before checking whether that lane can actually handle it. For example, if codex is installed but the task repo has no local checkout, _call_local_agent returns false and dispatch_tasks marks the task failed, so later capable lanes such as Jules or GitHub Actions never get a chance. The fleet path should filter by task capability or treat capability skips as still open rather than consuming the task as a failed dispatch.
Useful? React with 👍 / 👎.
| echo "── 4b. dispatch jules (within daily budget) ──" | ||
| python3 -m limen dispatch --agent jules --live --limit "${LIMEN_JULES_LIMIT:-10}" || true | ||
| echo "── 4. dispatch paid fleet (capacity-census gated, per-lane bounded) ──" | ||
| python3 -m limen dispatch --agent fleet --live --limit "${LIMEN_FLEET_LIMIT:-${LIMEN_LOCAL_LIMIT:-3}}" || true |
There was a problem hiding this comment.
With LIMEN_DISPATCH=1, this now live-dispatches the github_actions lane whenever the fleet census sees gh, but the router can assign any repo-backed task to that lane without proving the target repo has the configured limen-agent.yml workflow. In environments where gh is installed but most target repos lack that workflow, _call_github_actions returns false and dispatch_tasks marks those tasks failed; before this change metabolize did not dispatch the GitHub Actions lane at all, so these tasks were not converted into failures.
Useful? React with 👍 / 👎.
1 participant
Autonomous limen dispatch of task
FORCE-route-all-services.Extend route.py/dispatch so work fans across EVERY available paid agent: codex, claude, opencode, agy, gemini, jules, + copilot (FORCE-copilot-lane), + warp/oz (FORCE-warp-oz-lane), + GitHub Actions runners. Principle: no paid subscription/service sits idle while work exists. Add a 'capacity census' that lists every reachable agent each cycle.
Produced in an isolated worktree off origin — review before merge.