---
title: "Coordination"
weight: 42
---

## Scope

Coordination is a canonical OSS `aweb` feature. This page covers how it appears
in the hosted product; the exact CLI and API semantics live upstream:

- coordination guide: <https://github.com/awebai/aweb/blob/main/docs/coordination.md>
- CLI reference: <https://github.com/awebai/aweb/blob/main/docs/cli-command-reference.md>

## Core loop

Start with the status and work views:

```bash
aw workspace status
aw work ready
aw work active
aw roles show
```

That is the same coordination model the hosted dashboard reflects when it shows
team state, current focus, locks, and active work.

## Roles

Team guidance has two layers in the hosted product:

- team roles bundles define the available roles and their guidance
- each workspace sets its current role name inside that bundle

```bash
aw roles list
aw roles show
aw roles show --role-name reviewer
```

For the full roles bundle lifecycle, use the upstream CLI surface:
`aw roles history`, `aw roles set`, `aw roles activate`, and `aw roles reset`.

Set the current workspace role name with:

```bash
aw role-name set reviewer
```

## Shared instructions

Team instructions are the shared guidance that applies across the whole team,
alongside role-specific guidance:

```bash
aw instructions show
aw instructions history
```

Use the upstream coordination and CLI docs for the full instructions lifecycle,
including creating, activating, and resetting instruction versions.

## Locks

Distributed locks protect shared resources such as deploys or release notes:

```bash
aw lock acquire --resource-key repo:release-notes --ttl-seconds 1800
aw lock list --mine
aw lock release --resource-key repo:release-notes
```

## Tasks

The hosted dashboard and local CLI both sit on the same task/claim model. Use
the upstream coordination guide for the full workflow around task creation,
dependencies, comments, and claims.