Route Linear tickets to PRs across multiple repos
Onorca.dev is very similar but has a desktop UI that I prefer to herdr. Task: The author uses a hybrid workflow combining Orca.dev for manual tasks and Cyrus for automation. Cyrus receives inputs via Telegram/OpenClaw, routes tasks through a Linear control plane, and generates PRs across multiple repositories using label-based routing to select specific AI models. Orca.dev is used for hands-on work due to its desktop UI and native Linear/GitHub integrations, allowing the user to manually start workspaces for specific tickets or issues.; tools: OpenClaw. Human role: The original post does not say how a person stayed involved.; limitations: Orca and Herdr lack native integration for multi-project work, necessitating the Cyrus layer. The workflow relies on specific tools (OpenClaw, Cyrus, Linear, GitHub) and requires manual configuration of labels and routing rules. Source reliability is secondary (a forum comment), and the text does not specify costs, security implications, or failure handling for the automated PR generation..
Tools
Published on Agent Work Atlas:
Overview
Onorca.dev is very similar but has a desktop UI that I prefer to herdr.
Workflow
The author uses a hybrid workflow combining Orca.dev for manual tasks and Cyrus for automation. Cyrus receives inputs via Telegram/OpenClaw, routes tasks through a Linear control plane, and generates PRs across multiple repositories using label-based routing to select specific AI models. Orca.dev is used for hands-on work due to its desktop UI and native Linear/GitHub integrations, allowing the user to manually start workspaces for specific tickets or issues.
Reported result
The author reports that this setup makes them 'more hands off' regarding automated tasks. However, no quantitative metrics, success rates, or specific time savings are provided in the source. The effectiveness is described qualitatively as a preference for the desktop UI and the ability to handle multi-project work that Orca/Herdr alone could not.
Human role
The original post does not say how a person stayed involved.
Limitations
Orca and Herdr lack native integration for multi-project work, necessitating the Cyrus layer. The workflow relies on specific tools (OpenClaw, Cyrus, Linear, GitHub) and requires manual configuration of labels and routing rules. Source reliability is secondary (a forum comment), and the text does not specify costs, security implications, or failure handling for the automated PR generation.
Try it
Act as a DevOps agent to configure a multi-repo automation workflow. Inputs: [Linear Workspace URL], [GitHub Org Name], [Telegram Bot Token], [Cyrus Config File]. Steps: 1. Analyze the provided [Linear Workspace URL] to identify existing projects and ticket labels. 2. Draft a routing configuration for Cyrus that maps specific Linear labels to target GitHub repositories and AI models (e.g., 'backend' -> 'repo-api' -> 'codex-sol'). 3. Set up a Telegram/OpenClaw ingress rule to capture task requests. 4. Perform a dry run: Select one sample ticket from [Linear Workspace URL]. Simulate the routing process and generate a draft PR description for the corresponding [GitHub Org Name] repo. Do not push code. 5. Present the draft PR and routing logic to me for approval. 6. Upon my explicit confirmation, execute the actual PR creation. Constraints: Never auto-merge PRs. Always require human review for the first 5 tasks. If a label is missing, pause and ask for clarification. Output the final configuration as a JSON file and the sample PR as a Markdown diff.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.