Skip to content
sinc-LLMBook a 30-minute call

Public project · Claude · Codex · Grok · local

Olondunge

Route work across your installed agent CLIs.

A local MCP server for choosing an available lane, collecting bounded results and arranging a separate verification pass.

Apache-2.0

Software use follows the repository’s terms. Installation, integration and model usage are separate considerations.

Usage pattern
  1. Task + limits
  2. Available lane
  3. Collect + verify

A guide to how the project is used. Read its requirements and limits before installation.

Your starting point

Several agent CLIs or a local model endpoint with different strengths and costs.

Tools, model choices and result checks live in separate sessions.

The capability to add

Choose a suitable lane without manually moving every task between tools.

MCP allocation tools inspect available lanes, plan and dispatch jobs, then collect results and request blind verification.

What’s in the project

A tool you can inspect.

Capabilities

  • Claude, Codex, Grok and compatible local-model lanes
  • Explicit model, effort and task boundaries
  • Capped results, redaction and a job ledger

Requirements

  • Python 3.11+, uv and Linux or macOS
  • At least one supported CLI installed and logged in; a local endpoint for the local lane

Important limits

  • Available lanes depend on installed tools, account access and configuration.
  • CLI subscription or model usage costs still apply; this is not a hosted model subscription.

A useful fit

Consider this when…

Developers already using multiple agent CLIs who want a common allocation interface.

A different starting point

Choose another approach when…

Buyers expecting model accounts, provider credits or a managed cloud service.

Inspect the implementation

Public source, with a specific scope.

The repository and the files below show the implementation available to inspect. They do not establish results for your workflow.

Reviewed source snapshot: 174f762ceb0e.

Compatibility and behavior must be checked in your environment. No customer-result or quality-improvement guarantee is implied.

Code and implementation help

Choose the help you need.

Software. Apache-2.0. Read the repository’s terms and installation guide.

Setup and integration. Bring your current tools, a workflow and your desired result. Scope, fees, delivery and support are confirmed before work starts.

Operating costs. Existing CLI subscriptions, model-provider usage and hosting may apply depending on the tool and your configuration.

Compare published service scopes and prices ↗

Your next step

Inspect it. Then decide what to add.

Use the source and requirements to judge fit. If you want help adapting it to your workflow, start with a scoped conversation.

Discuss Olondunge setup ↗

No setup fee is agreed or payment taken on this page.

A closer look

Which scope fits your work?

Prices describe different engagements. Final scope, timing and fees are confirmed in the proposal.