repowiseopenrouterlabs/spawn

openrouterlabs / spawn

Spawn any agent, on any cloud

TypeScript★ 244

github.com/openrouterlabs/spawnIndexed at 1bec53eUp to date with upstream

About this codebase

378 files and 1,641 symbols in 6 modules, led by TypeScript (223 files) and Shell (92).

Built from the index

Code health

7.0out of 10Good

This codebase scores 7.0 out of 10 for code health, which we rate good. It also scores maintainability 8.1 and static performance 9.5 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 1 of 378 files are git hotspots, and they average 3.0 — which is where the fixes pay off most.

Use openrouterlabs/spawn in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

  1. 1.In Claude, open Customize → Connectors, click +, then Add custom connector. On a Team or Enterprise plan an owner adds it first under Organization settings → Connectors.
  2. 2.Paste the server URL below as the Remote MCP server URL, then click Add.
  3. 3.Click Connect. A Repowise sign-in window opens. Approve access.
  4. 4.Repowise's tools are now available in your Claude chats.

Connect with one click. Sign in with Repowise (OAuth), no API key to copy. Works in Claude on the web, desktop, and mobile.

Docs
bash
https://api.repowise.dev/mcp/openrouterlabs/spawn
Editors need an API key: sign in to create one.Sign in to connect

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is spawn put together?")
  • get_why("why is spawn structured this way?")

Explore spawn

How openrouterlabs/spawn works

The codebase has 378 files and 1,641 symbols in 6 modules, led by TypeScript, Shell and Terraform. Code health is 7.0 out of 10, rated good.

About this page

Get a page like this for your own codebase

Repowise built this map of openrouterlabs/spawn from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Index your repo freeSee how Repowise worksFree for 2 public repos, with a page like this one.

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.