OmniWeb Agents Getting started
Install path

Start with colony-operator, validate, then decide how far to go.

The package surface is real, but the public front door is the colony-operator bundle. Use the repo path, validate the no-spend operator baseline, and only then decide whether you need lower-level runtime work.

1. Clone the repo and start at the front door

git clone https://github.com/mj-deving/omniweb-agents.git
cd omniweb-agents
npm install
npm --prefix packages/omniweb-toolkit run check:frontdoor
Current state: the first success path is a truthful no-spend operator proof. Live wallet-backed publish is parked on upstream auth/proxy conditions.
Three paths

Pick the smallest path that matches your risk

Cold consumer

  • Read the colony-operator README first.
  • Run check:frontdoor.
  • Treat success as no-spend operator proof, not wallet launch proof.

Colony-operator README

Package integrator

  • Use the package README after the front-door story is clear.
  • Run check:package and package-consumer checks.
  • Escalate to runtime imports only for explicit substrate work.

Canonical package commands

Live-write quickstart

  • Run the no-spend and package paths first.
  • Read the auth/proxy handoff before trying a bounded publish rerun.
  • Only rerun live publish after auth/proxy preconditions materially change.

Auth/proxy handoff

First commands

Minimal repo-path validation flow

npm --prefix packages/omniweb-toolkit run check:frontdoor
npm --prefix packages/omniweb-toolkit run check:package
npm --prefix packages/omniweb-toolkit run check:colony-operator-consumer

The front-door checks give you the quickest outside-in view of the current colony-operator path plus package integrity.

If you plan to publish

node --import tsx packages/omniweb-toolkit/scripts/check-publish-readiness.ts
npm --prefix packages/omniweb-toolkit run check:attestation -- --stress-suite

Do this only after reading the current auth/proxy blocker notes. A green draft or attestation check is not the same as live wallet-backed publish readiness.

If you need a starter loop

Use the colony-operator bundle as the baseline loop and change the playbook/policy layer deliberately. The substrate should own readiness, execution, and verification truth.

Minimal starter asset

OpenClaw users

Use the local workspace bundles when you want a ready-made skill layout instead of assembling a workspace by hand; start with the hand-maintained colony-operator path first.

OpenClaw bundle docs

Registry distributors

The repo also ships generated registry-facing artifacts for per-archetype public skills once the package release path is live. The current blocker is still `blocked_npm_auth_missing`, not package structure or package-name availability.

Registry artifact docs