* Remove code comments and add the no-comments rule
Remove the comments from first-party code and configuration files:
TS/JS, JSX, CSS, SQL migrations, Swift, Kotlin, Gradle, shell,
Docker, systemd, Nix, YAML, TOML, JSONC and GritQL.
Keep only what a tool reads: license headers, shebangs, compiler
and lint directives, JSDoc types in plain .js files, generated file
headers, GritQL scope lines, the install-server.sh help text and the
openbot-boat-pre-stop marker. Vendored code, fixtures and released
schemas keep their comments.
Add the rule to AGENTS.md, and change the docs that asked for
comments. Add two i18n keys that only comments named to
RELEASED_SOURCE_KEYS.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Keep comments that are data in strings
The benchmark task files in opencode-free-models-bench.ts tell the
model what each function must do. The sample file and HTML page in
the two stories are display content. Put their comments back.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Keep released migrations and mobile native inputs unchanged
check:migrations compares each released migration with v0.73.0 byte
for byte, so restore src/backend/migrations. A change to a native
build input of apps/mobile makes a new runtime version, so restore
those files and the extra fingerprint sources.
List these files and the comment markers that a tool reads in
AGENTS.md. Remove the last requests for comments in
src/renderer/AGENTS.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Add roles that set the agents that members can use
The host keeps a set of roles for each server in
openbot-agent-access-v1.json. Each role gives each agent one level:
none, view, chat or manage. A member gets the highest level of Everyone
and of their roles. Owners and admins always get manage. The new Team API
capability agent-access-v1 reads and sets the roles, and the host checks
the level on the agent routes.
Server settings get a Roles tab on desktop and web. Each member row on
the Members page gets one menu for the server role and the roles.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Check roles on more routes and send events faster
- Answers to prompts, approvals and browser requests need the chat level.
- The memory inclusion route needs the manage level.
- A save drops the levels of deleted agents, so the file does not grow.
- A member removal reads the roles in the write lock.
- An event reads the roles once for each member, after the skip checks.
The shared conversation payload key holds all closed agents.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Copy the access of an agent to its duplicate
A duplicate now gets the levels of its source before clients see it, so the copy does not open memories that the roles close. Live Activity reads the member's current role at each send.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Keep the remote queue snapshot in one WebRTC frame
The mailbox keeps every finished delivery, and GET /v1/agents/:id/queue
sends all of them. After some weeks of use, the response is larger than
the 2 MiB WebRTC JSON frame. The host peer then sends
error.remote.responseTooLarge, and the phone and the web client cannot
read the queue (#2368).
Add the optional queue-window-v1 capability (protocol 7 only). When a
request advertises it, the queue and queue/edit responses keep all
queued, starting and running deliveries, and the newest finished
deliveries: at most 100, within WEBRTC_FRAME_BODY_BUDGET. The wire
shape and queue order do not change. A request without the capability
gets the full list, so the released contract stays the same.
Add scripts/queue-window-e2e.ts. It seeds long histories, queued,
editing, running and failed deliveries on a real mailbox store, reads
them through the real route and the V7 WebRTC frame encoder, and writes
.openbot-build/queue-window-e2e/report.json.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Keep failed deliveries in the queue window
The window kept only the newest 100 finished deliveries. A failed message older than 100 later deliveries lost its failure reason on the phone and the web client. Now the window keeps every failed, interrupted and cancelled delivery while it fits in the frame. Only completed deliveries leave it. The E2E script checks an old failure before 150 completed deliveries.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>