Agentlas OS plugin
A layer over coding agents that assembles a temporary specialist team per task inside Claude Code, Codex, Cursor and Gemini
- 1,453 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The install script edits plugin and MCP config in the agent hosts
- Orchestrates several agents that run tools
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/agentlas-osDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The install script edits plugin and MCP config in the agent hosts
- Orchestrates several agents that run tools
This is third-party code. Review the repository files before installing.
What it does
Agentlas OS installs into the agent hosts you already use and adds orchestration: for a given task it selects and assembles a temporary team of specialist agents, for example frontend and backend, and disbands it afterward. Specialists live in a hub, and a separate orchestrator spins up per task. It runs locally and with any model, and installs with a single script that verifies the release checksum and writes plugin and MCP config into the hosts it finds. It bundles a large set of skills and plugins.
Who it is for. For developers who want to add agent-team orchestration to their usual tools.
Good fit when
- You want a specialist agent team assembled per task
- You need orchestration on top of Claude Code, Codex, Cursor or Gemini
- You want a local approach not tied to a single model
Not a fit when
- A single agent without team orchestration is enough
- You do not want to run an install script that edits host configuration
Example request
Assemble a frontend and backend specialist team for this task and split up the workLimitations
Installation runs a script that writes plugin and MCP config into the agent hosts it finds, which is worth understanding before running. Some features tie into the Agentlas cloud and desktop. The orchestration overhead is not worth it for every task.
How to disable. Remove the ~/.agentlas directory and the wrappers from ~/.local/bin, and undo the plugin and MCP entries written into the host configs.
FAQ
Which hosts does it work in?
Inside Claude Code, Codex, Cursor, Gemini and others; the installer finds supported hosts on the machine.
Where does the installer write?
It puts the runtime in ~/.agentlas, wrappers in ~/.local/bin and plugin and MCP config into the found hosts, nothing outside the home folder.
Discussion
No questions or reviews yet.
Related
PluginsA bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
A local dashboard for running many agents across machines: memory, code graph and agent-to-agent messaging
A multi-agent harness that verifies results by artifacts: stop hooks, an independent judge and an event log for Claude Code, Codex, Cursor and more
A self-hosted AgentOS for one workspace: plan-mode chat, private knowledge base, MCP tools, skills, memory and a sandbox
Orchestrator plugin for OpenCode and Codex CLI: multiple agents, hooks, built-in MCPs, ultrawork mode and hash-anchored edits
A process kit for agents: a skill router, project memory in a DEV folder and result verification before saying done.
README in short
The README presents Agentlas OS as a layer over coding agents that assembles a temporary specialist team per task and disbands it afterward. Specialists live in a hub, a separate orchestrator spins up per task, all local and with any model. Installation is a single script that verifies the release checksum, installs the runtime into the home folder and writes plugins and MCP into the found hosts. Apache-2.0 licensed.