[limen LIMEN-004] Open Codex task two

[4444J99]

Autonomous limen dispatch of task LIMEN-004.

Produced in an isolated worktree off origin — review before merge.

Summary by Sourcery

Enhancements:

• Add support for using a LIMEN_DISPATCH_CMD environment override for agent dispatch while retaining the existing agent-dispatch fallback behavior.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds support for a custom LIMEN_DISPATCH_CMD environment variable that, when set, is used directly for non-jules agents before falling back to local agents or the default 'agent-dispatch' command, slightly reordering the dispatch resolution logic.

Flow diagram for updated call_agent_dispatch logic

flowchart TD
    start([call_agent_dispatch])
    jules{agent == 'jules'}
    env{LIMEN_DISPATCH_CMD is set}
    local{agent in _LOCAL_AGENTS}
    default_cmd([Use 'agent-dispatch'])
    run_env([Run _run_cmd with LIMEN_DISPATCH_CMD])
    run_local([Call _call_local_agent])
    run_jules([Call _call_jules])

    start --> jules
    jules -->|yes| run_jules
    jules -->|no| env
    env -->|yes| run_env
    env -->|no| local
    local -->|yes| run_local
    local -->|no| default_cmd
    default_cmd --> run_env

Loading

File-Level Changes

Change	Details	Files
Support an explicit LIMEN_DISPATCH_CMD override for non-jules agents and adjust dispatch resolution order.	After handling the special-case 'jules' agent, read LIMEN_DISPATCH_CMD from the environment and, if set, dispatch using that command with the built prompt before checking local agents. Change the default behavior for non-local agents so that LIMEN_DISPATCH_CMD is no longer read with a default, instead always using the literal 'agent-dispatch' command when the environment variable is not set or was already handled. Ensure the prompt is only built once per dispatch path and passed along with the agent to the selected command runner.	cli/src/limen/dispatch.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[gemini-code-assist]

Code Review

This pull request modifies the agent dispatch logic in cli/src/limen/dispatch.py by checking and executing LIMEN_DISPATCH_CMD before verifying if the agent is a local agent. However, this change bypasses the local agent check, which violates the Worktree Isolation protocol. It is recommended to restore the _LOCAL_AGENTS check before applying LIMEN_DISPATCH_CMD to ensure local agents run in isolated git worktrees.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Bypassing the _LOCAL_AGENTS check when LIMEN_DISPATCH_CMD is set violates the Worktree Isolation protocol. Local agents (such as codex, opencode, etc.) must run in isolated git worktrees via _call_local_agent to prevent parallel task conflicts in the shared working directory. Checking LIMEN_DISPATCH_CMD first completely bypasses this isolation.

Please restore the check for _LOCAL_AGENTS before checking or applying LIMEN_DISPATCH_CMD.

Suggested change

	dispatch_cmd = os.environ.get("LIMEN_DISPATCH_CMD")
	if dispatch_cmd:
	prompt = _build_prompt(task)
	return _run_cmd([dispatch_cmd, agent, prompt], task, dry_run)
	if agent in _LOCAL_AGENTS:
	return _call_local_agent(agent, task, dry_run)
	dispatch_cmd = os.environ.get("LIMEN_DISPATCH_CMD", "agent-dispatch")
	dispatch_cmd = "agent-dispatch"
	prompt = _build_prompt(task)
	cmd = [dispatch_cmd, agent, prompt]
	return _run_cmd(cmd, task, dry_run)
	if agent in _LOCAL_AGENTS:
	return _call_local_agent(agent, task, dry_run)
	dispatch_cmd = os.environ.get("LIMEN_DISPATCH_CMD", "agent-dispatch")
	prompt = _build_prompt(task)
	cmd = [dispatch_cmd, agent, prompt]
	return _run_cmd(cmd, task, dry_run)

References

1. Execution Protocols - 1. Worktree Isolation: Instead of cloning or checking out branches in the main repository checkout, the Conductor Swarm MUST spawn tasks in isolated git worktrees. ^(link)

[sourcery-ai]

Hey - I've left some high level feedback:

• The new ordering means LIMEN_DISPATCH_CMD is now used for agents in _LOCAL_AGENTS instead of _call_local_agent, which changes behavior; consider whether local agents should still bypass external dispatch and, if so, move the _LOCAL_AGENTS check before the LIMEN_DISPATCH_CMD branch.
• You now build the prompt twice along different branches; consider refactoring to compute prompt = _build_prompt(task) once before the dispatch command selection to avoid duplication.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new ordering means `LIMEN_DISPATCH_CMD` is now used for agents in `_LOCAL_AGENTS` instead of `_call_local_agent`, which changes behavior; consider whether local agents should still bypass external dispatch and, if so, move the `_LOCAL_AGENTS` check before the `LIMEN_DISPATCH_CMD` branch.
- You now build the prompt twice along different branches; consider refactoring to compute `prompt = _build_prompt(task)` once before the dispatch command selection to avoid duplication.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 07550bf03a

ℹ️ 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".

[chatgpt-codex-connector]

Keep local lanes on the isolated dispatch path

When LIMEN_DISPATCH_CMD is set in an environment that dispatches a local lane, this branch runs before agent in _LOCAL_AGENTS, so codex/opencode/agy/claude no longer reach _isolated_local_run and therefore skip the worktree → commit → push → PR flow used by scripts/metabolize.sh. Any wrapper that exits 0 will still make dispatch_tasks mark the task dispatched and spend budget, but without the promised reviewable PR or live-checkout isolation; please keep local agents on _call_local_agent unless LIMEN_ISOLATION=off is explicitly requested.

Useful? React with 👍 / 👎.

[4444J99]

superseded by #31 (newest dispatch of same fleet task: LIMEN-004)