Skip to main content

Isolated dev sessions for multiple local trigger dev instances

Feature Request

Right now, multiple trigger dev instances for the same project share one queue, so any instance can run any task and they end up “stealing” each other’s work. The ask is to support something like preview branches, but for the dev environment: separate dev sessions (e.g. a session id or “dev branch”) so each local instance only runs tasks triggered from that same session. That would let you run several work trees or app copies in parallel (e.g. with Codex/Claude) without tasks from one ending up running in another.

Posted by Iss Haddad ·
Status: Completed2 comments

Comments2

  • mattaitken

    Team•

    Jul 3

    This is now available in v4.5.

    Read the docs here
    https://trigger.dev/docs/deployment/dev-branches

    Or just add --branch to your next dev server:

    npx trigger.dev@latest dev --branch my-feature

    And clean up old ones:

    npx trigger.dev@latest dev archive --branch my-feature

  • Ido Kadosh

    •

    Apr 27

    Is there a work around for this?

    our current workflow is running only one worktree in parallel, the only blocker is trigger.dev currently.

    Is there a way to handle this for Claude + git worktrees in the meantime?