Plexus

Rows of horizontal lines lifted over a hidden stepped platform, so the terraces show as steps in the lines, with a bright core on the top tier.Rows of horizontal lines lifted over a hidden stepped platform, so the terraces show as steps in the lines, with a bright core on the top tier.

tool discovery and wiring for AI agents

Plexus is a local CLI and MCP discovery layer for agent toolchains. It reads each tool's declared inputs and outputs, finds compatible connections, and produces dependency graphs or runnable pipeline scripts; it probes registered Flywheel lanes only when explicitly requested.

Inspect sourceRun or verifyRead evidence
Status
active
Access
install
Release
0.2.2 on PyPI as plexus-mesh; latest GitHub release v0.2.1
Checked
2026-09-26

Listed in the catalog under

Who it is for

Audiences

  • agent-system engineers
  • software engineers

Deployment contexts

  • controlled agent workflows
  • local development workspaces

Inputs and outputs

Inputs

  • tool and lane manifests
  • desired inputs and outputs
  • pipeline constraints

Outputs

  • capability graphs
  • producer-consumer wiring plans
  • runnable pipeline scripts
  • lane health results

Run or evaluate

See it work, step by step An animated walkthrough with the real commands and output from the repository.

Entrypip install plexus-mesh==0.2.2; plexus discover --builtin
Verificationplexus plan --goal crucible --builtin > plan.json; plexus verify --plan plan.json --builtin

Inspect the public source

Architecture and relationships

Related records

  • Relaycoding agent that acts within granted permissions
  • Forummulti-agent orchestration engine
  • Flywheelverified-inference platform and desktop client
Architecture, dependencies, and relationship notes

Dependencies

None declared in the public registry.

Relation-backed claims

  • Flywheel includes Plexus as a lane
    Flywheel 1.0.4 declares and launches Plexus 0.2.2 as its capability-mesh and tool-wiring MCP lane. Plexus can probe registered lanes when explicitly requested, but declared mesh edges are not semantic interoperability proof.

Current evidence

plexus-mesh 0.2.2 on PyPI

Verified

How we know

PyPI serves plexus-mesh 0.2.2, uploaded on 22 September 2026 (Pacific time). A clean virtual environment installed it from PyPI and plexus --version reported 0.2.2. Version 0.2.2 has no GitHub release.

Plexus v0.2.1

Verified

How we know

The v0.2.1 GitHub release was published on 17 September 2026 (Pacific time) and is the latest GitHub release.

Plexus public source

Verified

How we know

The public source metadata identifies plexus-mesh 0.2.0, and the README describes manifest discovery, wiring plans, route scripts, graphs, MCP exposure, and explicit lane probe commands; no GitHub release tag was returned.

Limitations and authorization boundaries

  • Manifest edges and source pointers remain declared claims until followed or probed.
  • Probe mode checks registered lane reachability, not semantic interoperability or output quality.

Authorization boundary. A wiring plan does not grant authority to execute any connected capability.