Skip to content
Lasso logo Lasso
Purple star wrapped with a golden lasso

LASSO / AGENT-NATIVE MONOREPOYour repos.
Your agents.
One workspace.

Lasso is an extensible agent-native monorepo for multi-agent, multi-repo development.
Get started Explore plugins
01 / IN PLAIN ENGLISH

A shared map for AI coding work.

Lasso gives every agent the same answer to three basic questions: which repositories exist, where should I work, and which rules and capabilities should I load?

01

Find every repository

Register independent repositories or true monorepo subdirectories in one small, readable catalog.

project-defs/
02

Work without collisions

Give each task its own Git worktree while stable checkouts remain clean integration inputs.

worktrees/<project>/<task>
03

Load the right capabilities

Share project rules, language conventions, skills, hooks, and checks across supported agent runtimes.

plugins/ + modules/
02 / HOW IT WORKS

From repository list to isolated task in three steps.

Lasso coordinates the workspace around your tools. Git still owns branches and worktrees. Each project still owns its build, test, and deploy commands.

  1. 01
    CREATE THE WORKSPACE

    Choose your runtimes and starter modules.

    This creates the shared contract, lock file, runtime adapters, and core plugin.

    lasso init ~/my-workspace —runtime=codex,claude
  2. 02
    REGISTER REPOSITORIES

    Declare identity, then materialize stable checkouts.

    The registry stores repository identity—not a second build system or deployment DSL.

    lasso project add —project=app —repo-url=…
  3. 03
    START A TASK

    Create an isolated surface and let the agent execute.

    The agent follows the nearest project guidance and uses the capabilities installed in the workspace.

    lasso worktree create feature-login —project=app
Lasso coordinates.Agent runtimes own goals and sessions.Git owns branches and worktrees.Projects own build, test, and deploy.Read the core mechanism
03 / MULTI-REPO + MULTI-AGENT

One contract across repositories and agent providers.

External repositories stay independent. Subdirectory projects can remain a true monorepo. Codex is the baseline runtime; Claude and Grok follow through shared skills and thin adapters.

  • One identity catalog across repositories
  • One worktree convention across machines
  • One canonical skill body across runtimes
  • Project-specific constraints remain local
See runtime support
ONE LASSO WORKSPACE
CodexClaudeGrok
Lassoregistry · worktrees · modules
web-appapidocs
04 / PLUGIN ECOSYSTEM

Extend the workspace without forking the core.

Lasso modules are versioned capability packs. Install only what your workspace needs; every installed version is recorded in lasso.lock.toml.

CONVENTIONS

Teach agents your engineering language.

Shared guidance for Go, Rust, Nix, and repository-specific working rules.

lang-golang-rustlang-nix
CAPABILITIES

Add deterministic workspace checks.

Scripts and contracts that agents can run and CI can verify consistently.

docs-index
PLUGINS

Give agents reusable workflows.

Skills, hooks, and runtime manifests for security, memory, and session safety.

securityhooksmemory
INSTALL A MODULEOne command. Explicit state change.

The payload is copied into the workspace, its version is pinned, and supported runtime marketplaces are refreshed.

workspace$ lasso module add security✓ security 0.2.0 installed
Explore the extension model
05 / FIRST WORKSPACE

Start with one workspace and one repository.

Add more repositories, providers, and plugins only when the work needs them.

Open the quick start View on GitHub
lasso / quick start
$ lasso init ~/my-workspace --runtime=codex

$ lasso project add --project=app --repo-url=git@github.com:you/app.git
$ lasso setup --only=app
$ lasso worktree create first-task --project=app

✓ isolated workspace ready