← Back to Skills Marketplace
cryptocana

Agent Os

by Novaiok · GitHub ↗ · v0.1.0
cross-platform ⚠ suspicious
636
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install agent-os
Description
Persistent agent operating system for OpenClaw. Agents remember across sessions, learn from experience, coordinate on complex projects without duplicate work.
README (SKILL.md)

Agent OS — Persistent Agent Operating System

Agents that remember. Learn. Coordinate.

What It Does

Agent OS enables multi-agent project execution with persistent memory:

  • Agent Memory — Each agent remembers past tasks, lessons learned, success rates
  • Task Decomposition — Break high-level goals into executable task sequences
  • Smart Routing — Assign tasks to agents based on capability fit
  • Execution Tracking — Live progress board showing what every agent is doing
  • State Persistence — Project state survives restarts (resume mid-project)

Quick Start

Installation

clawhub install nova/agent-os

Basic Usage

const { AgentOS } = require('agent-os');

const os = new AgentOS('my-project');

// Register agents with capabilities
os.registerAgent('research', '🔍 Research', ['research', 'planning']);
os.registerAgent('design', '🎨 Design', ['design', 'planning']);
os.registerAgent('dev', '💻 Development', ['development']);

os.initialize();

// Run a project
const result = await os.runProject('Build a feature', [
  'planning',
  'design',
  'development',
]);

console.log(result.progress); // 100

Core Concepts

Agent

Persistent worker with:

  • Memory — Past tasks, lessons learned, success rates
  • State — Current task, progress, blockers
  • Capabilities — What it's good at (research, design, development, etc.)

TaskRouter

Decomposes goals into executable tasks:

  • Breaks "Build a feature" into: plan → design → develop → test
  • Matches tasks to agents based on capability fit
  • Tracks dependencies (task A must finish before task B)

Executor

Runs tasks sequentially:

  • Assigns tasks to agents
  • Tracks progress in real-time
  • Persists state so projects survive restarts
  • Handles blockers and errors

AgentOS

Orchestrates everything:

  • Register agents
  • Initialize system
  • Run projects
  • Get status

Architecture

AgentOS (top-level orchestration)
├── Agent (persistent worker)
│   ├── Memory (lessons, capabilities, history)
│   └── State (current task, progress)
├── TaskRouter (goal decomposition)
│   ├── Templates (planning, design, development, etc.)
│   └── Matcher (task → agent assignment)
└── Executor (task execution)
    ├── Sequential runner
    ├── Progress tracking
    └── State persistence

State Persistence

All state is saved to the data/ directory:

  • [agent-id]-memory.json — Agent knowledge base
  • [agent-id]-state.json — Current agent status
  • [project-id]-project.json — Project task list + status

This means: ✅ Projects survive restarts ✅ Agents remember past work ✅ Resume mid-project seamlessly

File Structure

agent-os/
├── core/
│   ├── agent.js          # Agent class
│   ├── task-router.js    # Task decomposition
│   ├── executor.js       # Execution scheduler
│   └── index.js          # AgentOS class
├── ui/
│   ├── dashboard.html    # Live progress UI
│   ├── dashboard.js      # Dashboard logic
│   └── style.css         # Styling
├── examples/
│   └── research-project.js  # Full working example
├── data/                 # Auto-created (persistent state)
└── package.json

API Reference

AgentOS

new AgentOS(projectId?)
registerAgent(id, name, capabilities)
initialize()
runProject(goal, taskTypes)
getStatus()
getAgentStatus(agentId)
toJSON()

Agent

startTask(task)
updateProgress(percentage, message)
completeTask(output)
setBlocker(message)
recordError(error)
learnLesson(category, lesson)
reset()
getStatus()

TaskRouter

decompose(goal, taskTypes)
matchAgent(taskType)
getTasksForAgent(agentId, tasks)
canExecuteTask(task, allTasks)
getNextTask(tasks)
completeTask(taskId, tasks, output)
getProjectStatus(tasks)

Executor

initializeProject(goal, taskTypes)
execute()
executeTask(task)
getStatus()

Example: Research + Design + Development

See examples/research-project.js for the canonical example:

npm start

This demonstrates:

  • ✅ 3 agents with different capabilities
  • ✅ 12 tasks across 3 phases (planning, design, development)
  • ✅ Sequential execution with progress tracking
  • ✅ State persistence to disk
  • ✅ Final status report

Expected output:

✅ Registered 3 agents
📋 Task Plan: 12 tasks
🚀 Starting execution...
✅ [Task 1] Complete
✅ [Task 2] Complete
...
📊 PROJECT COMPLETE - 100% progress

What's Coming (v0.2+)

  • HTTP server + live dashboard
  • Parallel task execution (DAG solver)
  • Capability learning system (auto-score agents)
  • Smart agent routing (match to best agent)
  • Failure recovery + retry logic
  • Cost tracking (token usage per agent)
  • Human checkpoints (review high-risk outputs)

Philosophy

Agents should remember what they learn.

Most agent frameworks are stateless. Agent OS keeps persistent memory so agents:

  1. Remember — No redundant context resets
  2. Learn — Capability scores improve over time
  3. Coordinate — Shared state prevents duplication
  4. Cost less — Less context = cheaper API calls

License

MIT


Built with ❤️ by Nova for OpenClaw

See README.md and ARCHITECTURE.md for complete documentation.

Usage Guidance
This skill appears coherent: it implements a local persistent multi-agent orchestrator and only writes JSON state files under its data/ directory. Before installing, review package.json (for any postinstall scripts), and confirm you are comfortable with project/agent data being stored on the host where the skill runs. If you plan to run real agents or connect to external AI services later, double-check any future changes that introduce network calls or credential requirements. If you need stricter isolation, run the skill in a sandboxed environment or review/modify the paths where it writes data.
Capability Analysis
Type: OpenClaw Skill Name: agent-os Version: 0.1.0 The skill bundle is classified as suspicious due to a critical path traversal vulnerability in `core/agent.js` and `core/executor.js`. The `id` and `projectId` parameters, which are user-controlled, are directly used in `path.join` to construct file paths for persistent storage without sanitization. This allows an attacker to register an agent or initialize a project with a specially crafted ID (e.g., containing `../`) to write arbitrary files to arbitrary locations on the host system, potentially leading to Remote Code Execution (RCE). While the code's stated purpose is benign (persistent agent system), this lack of input sanitization represents a significant security flaw that could be exploited.
Capability Assessment
Purpose & Capability
Name/description describe a persistent multi-agent orchestrator; the repository contains Agent, TaskRouter, Executor, index, UI and example files that implement exactly that functionality. There are no unrelated required binaries or environment variables.
Instruction Scope
Runtime instructions and API examples are consistent with the code. The SKILL.md and code explicitly state that state is persisted to a local data/ directory and the code reads/writes JSON files there; this is expected for a persistent agent OS but you should be aware project data (goals, outputs, agent memories) will be written to disk under the skill's directory.
Install Mechanism
This is an instruction-and-code package with no install spec in the skill metadata. No remote installers, downloads, or external release hosts are used in the metadata provided. The presence of package.json implies npm-style usage; review package.json for scripts before running installs.
Credentials
No environment variables, credentials, or config paths are required. The code only uses filesystem I/O under the skill's ../data path and standard Node.js modules (fs, path). There are no requests for unrelated tokens or secrets.
Persistence & Privilege
The skill persists state to disk (data/*.json) which is necessary for its stated goal. It does not request 'always: true' and uses default autonomous-invocation settings. Autonomous invocation is normal; because this skill stores persistent project and agent data locally, consider whether you want that data persisted on the host running the agent.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install agent-os
  3. After installation, invoke the skill by name or use /agent-os
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Agent OS 0.1.0 — Initial Release - Introduces a persistent multi-agent operating system for OpenClaw. - Agents remember tasks, lessons learned, and success rates across sessions. - Supports smart task decomposition, agent assignment, and execution tracking with live progress. - Full state persistence: agents and project state survive restarts and can resume mid-project. - API includes agent management, project orchestration, and extensible task routing. - Comes with a working multi-agent example, file structure, and clear templating for future growth.
Metadata
Slug agent-os
Version 0.1.0
License
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Agent Os?

Persistent agent operating system for OpenClaw. Agents remember across sessions, learn from experience, coordinate on complex projects without duplicate work. It is an AI Agent Skill for Claude Code / OpenClaw, with 636 downloads so far.

How do I install Agent Os?

Run "/install agent-os" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Agent Os free?

Yes, Agent Os is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Agent Os support?

Agent Os is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Agent Os?

It is built and maintained by Novaiok (@cryptocana); the current version is v0.1.0.

💬 Comments