Multi-Repository Setup

Route issues from a single Linear project to multiple Git repositories. Useful when your team splits work across frontend, backend, infrastructure, or service repos.

How routing works

Risoluto matches each incoming issue against a set of routing rules. Rules are evaluated in order:

Label match — if the issue has a label that matches a route, that route wins
Prefix match — the issue identifier prefix (e.g., FE-, BE-) selects the repo
Default — if nothing matches, the repo configured during setup is used

Configure routes

Define your repos

Add routes via the setup wizard at /setup, or use the API directly.

# Frontend repo for all FE-* issues
curl -s -X POST http://127.0.0.1:4000/api/v1/setup/repo-route \
  -H 'Content-Type: application/json' \
  -d '{
    "prefix": "FE-",
    "url": "https://github.com/org/frontend.git",
    "default_branch": "main"
  }'

# Backend repo for all BE-* issues
curl -s -X POST http://127.0.0.1:4000/api/v1/setup/repo-route \
  -H 'Content-Type: application/json' \
  -d '{
    "prefix": "BE-",
    "url": "https://github.com/org/backend.git",
    "default_branch": "main"
  }'

# Route any issue labeled "infra" to the infrastructure repo
curl -s -X POST http://127.0.0.1:4000/api/v1/setup/repo-route \
  -H 'Content-Type: application/json' \
  -d '{
    "label": "infra",
    "url": "https://github.com/org/infrastructure.git",
    "default_branch": "main"
  }'

{
  "repos": [
    {
      "prefix": "FE-",
      "url": "https://github.com/org/frontend.git",
      "default_branch": "main"
    },
    {
      "prefix": "BE-",
      "url": "https://github.com/org/backend.git",
      "default_branch": "main"
    },
    {
      "label": "infra",
      "url": "https://github.com/org/infrastructure.git",
      "default_branch": "main"
    }
  ]
}

Verify routes

curl -s http://127.0.0.1:4000/api/v1/setup/repo-routes | jq

Expected output:

[
  { "prefix": "FE-", "url": "https://github.com/org/frontend.git", "default_branch": "main" },
  { "prefix": "BE-", "url": "https://github.com/org/backend.git", "default_branch": "main" },
  { "label": "infra", "url": "https://github.com/org/infrastructure.git", "default_branch": "main" }
]

Test with a real issue

Create a Linear issue with identifier FE-42 and move it to In Progress. Confirm Risoluto clones the frontend repo for the agent workspace.

# Check which repo was cloned
curl -s http://127.0.0.1:4000/api/v1/FE-42 | jq '.workspace'

Use identifier prefixes (FE-, BE-) for stable team-to-repo mapping. Use labels for per-issue overrides — for example, when a backend developer needs to fix a frontend bug.

Managing routes

# List all routes
curl -s http://127.0.0.1:4000/api/v1/setup/repo-routes | jq

# Remove a route by index
curl -s -X DELETE http://127.0.0.1:4000/api/v1/setup/repo-route/0

Workspace strategy

When using the worktree strategy with multiple repos, each repository gets its own bare clone. Worktrees are created per-issue from the bare clone, sharing the Git object store for efficiency.

curl -s -X PUT http://127.0.0.1:4000/api/v1/config/overlay \
  -H 'Content-Type: application/json' \
  -d '{"workspace":{"strategy":"worktree","root":"../risoluto-workspaces"}}'

With the directory strategy, each issue gets a full git clone. For large repos, worktree saves significant disk space and clone time.

What’s Next

Custom Sandbox

Build a Docker image with project-specific tools and runtimes.

Configuration

Full config reference for workspace, agent, and routing options.

Monitoring Stack

Set up Prometheus and Grafana for multi-repo visibility.

Get Started

Core Concepts

Guides

Recipes

Operating

Multi-Repository Setup

How routing works

Configure routes

Managing routes

Workspace strategy

What’s Next

Custom Sandbox

Configuration

Monitoring Stack

​How routing works

​Configure routes

​Managing routes

​Workspace strategy

​What’s Next

Custom Sandbox

Configuration

Monitoring Stack

How routing works

Configure routes

Managing routes

Workspace strategy

What’s Next