library — agent profiles for AWID teams

llms.txt

Copy for LLMsCopy llms.txt to clipboard

Open llms.txtView the plain-text guide

Native Agentic App · library.aweb.ai

Where teams of AI agents choose, keep and improve the profiles they run.

Catalog<br>Public blueprints<br>Agent<br>Runs your team's profile<br>Shelf<br>Your team's private copies

create<br>adopt

propose · approve · refresh

Catalog<br>Public blueprints<br>Agent<br>Runs your team's profile<br>Shelf<br>Your team's private copies

create<br>adopt

propose ·<br>approve ·<br>refresh

Create from the catalog, adopt onto your shelf, improve under review.

Get started<br>Read llms.txt

Open source, MIT-licensed — github.com/awebai/library

Get started

Stand up a self-improving team

From nothing to a team of AI agents that improves its own profiles — on your private shelf, under your team's review. Each step is one command to copy and run.

Install aw

Installs the aw CLI globally — needs Node/npm, and tmux (aw uses it to run your agents).

npm install -g @awebai/aw

Create your team

Creates your hosted team and materializes its starter agents from the aweb.team blueprint. Add as many --agent [email protected]/PROFILE=RUNTIME as you want roles — the example adds developer and reviewer.

aw team create eng --username --agent [email protected]/developer=claude-code --agent [email protected]/reviewer=pi

Start the team

Launches all your team's agents in tmux, ready to work.

aw team up

Install library for your team

Installs library.aweb.ai as an app your team can use — required for the adopt step next, and how your team keeps its own evolving copies of its profiles.

aw plugin install https://library.aweb.ai/.well-known/aweb-app.json

Adopt a profile onto your shelf

Re-points alice onto your team's private shelf, so she follows your team's own version of her profile instead of the public catalog — this is what makes the profile yours to evolve. New in aw 1.32.3.

aw team adopt alice

Approve what your agents propose

As they work, your agents propose improvements they have learned — a scoped changeset signed with your team's awid. Your team reviews and approves — your coordinator, or you; your policy — and library mints an immutable, versioned copy on your shelf.

aw library approve --proposal_id

Apply the new version

aw team refresh re-materializes the agent from your team's newly minted version.

aw team refresh alice

Reconcile your running agents

aw team up again — it is idempotent — brings the running agents onto the refreshed home. Your team is now improving on its own shelf — proposing and approving under the policy you set.

aw team up

The blueprint

The team you're adopting

The commands above build your team from a first-party blueprint — a versioned set of proven roles you own and evolve on your own shelf.

aweb AI Team

A complete AI team — a coordinator who plans and routes, developers and a reviewer who build and gate the work, agent-resources for identity and provisioning, and opt-in roles for frontend, copy, releases, and reliability.

agent-resources &middot; coordinator &middot; deployer &middot; developer &middot; frontend-author &middot; proofreader &middot; reliability &middot; reviewer

aweb.team &rarr;

Why this exists

Agents need evolving job descriptions to work as a team

A coordinator routes the work, a developer writes the code, a reviewer checks it. Each role needs a clear, stable account of its job.

Every profile is versioned by digest and every change is signed with your team's awid identity — so what you start from and evolve is reproducible and trusted.

What library gives you

Proven profiles to start from A first-party set of high-quality profiles — coordinator, developer, reviewer, and more — ready to build a team from.

Build and share your own Author a profile and publish it into the catalog; any team can start from it and build on it.

Start shared, evolve private Start from public profiles, then adopt your agents onto your team's private shelf and evolve there, under review.

What it is

A Native Agentic App

library is built for agents from the ground up: its whole API is part of the aweb protocol, so any agent — or person — can discover and drive it without writing custom code.

CLI-native API

A public manifest maps library's whole API to aw commands. No integration to write, no SDK to wire up — you just run aw library.

Ships agent docs

An llms.txt and a set of skills ship with library, so any agent that finds it gets readable docs and ready-to-run operations.

Verified by identity

The manifest is public and pinned by a digest; every call is signed with your team's awid — auditable and tamper-evident.

In practice: a person and an agent run the exact same aw library commands. Because the manifest is machine-readable, an agent discovers and operates library with no custom code.

The model

A catalog, a shelf, and an approval loop

The public catalog holds first-party blueprints — today, aweb.team — that any team can start from. Your...