---
title: "Events & Control"
weight: 42
---

## Scope

Events and runtime control are mounted OSS `aweb` surfaces. `aweb-cloud` does
not define a separate hosted event protocol.

Canonical references live upstream:

- coordination guide: <https://github.com/awebai/aweb/blob/main/docs/coordination.md>
- `aw run` guide: <https://github.com/awebai/aweb/blob/main/docs/aw-run.md>
- server API reference: <https://github.com/awebai/aweb/blob/main/docs/server-api-reference.md>

## Hosted path

On the hosted service, identity-bound clients use the mounted OSS event stream
under `/api`, for example:

```text
GET /api/v1/events/stream
```

`aw run`, `aw notify`, and other local runtime flows consume those same OSS
wakeups and control signals.

## What this means in practice

- browser/dashboard features reflect the same underlying coordination state
- local CLI workspaces still use the canonical OSS event and control model
- exact payloads and tool semantics should be read from the upstream refs, not
  maintained as a second copy here