* 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>
* Set the virtual display size of self-hosted and Docker servers
Add OPENBOT_DISPLAY_SIZE (WIDTHxHEIGHT, 640x480 to 2576x2576) for the
virtual display that computer use reads: --display-size at the install,
the key in /opt/OpenBot/hosted/openbot.env, or a container variable. A
value that is not valid writes a warning, and the server starts with the
default. The install refuses it. A reinstall keeps the size.
The default is now 1920x1080 (before: 1280x800). Claude 4.7 and later
and Codex read a 1080p screenshot at full size. The boat desktop of a
hosted server does not change.
Part 1 of #2318.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Keep 1280x800 as the default server display size
A click test with the free OpenCode models hit 4 of 14 at 1920x1080 and
12 of 13 at 1280x800. At 1920x1080 the driver makes window screenshots
smaller, and some models then send screen pixels. 1920x1080 stays
available with OPENBOT_DISPLAY_SIZE and --display-size.
Part 1 of #2318.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Read the last openbot.env line when it has no newline
A hand-written OPENBOT_DISPLAY_SIZE line with no newline at the end of
the file was ignored, with no warning.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Start a hosted server before the disk restore when a release is ready
After a wake, boat restores the disk lazily for about 3.5 minutes. The
apply unit waited for the restore when a release was staged, so OpenBot
started only after it. The unit now runs `boot`, which skips a staged
release during the restore. OpenBot asks root to stage the release, which
waits for the restore, and installs it when the server is idle and no
client used it for 5 minutes. openbot.service also starts with lightdm,
about 8 seconds before boat starts the other enabled units.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Keep the hosted wake safe after a failed boot and during reading
- `boot` does nothing while OpenBot runs. boat starts the apply unit a
second time after a wake, and a failed `boot` was not active then.
- Self-hosted setup releases the update lock before it starts OpenBot,
because the start runs `boot`, which waits for the lock.
- The automatic install also waits 5 minutes after the start while a
client is connected, because a member who only reads is not in use.
- Remove the `client-use` label: `host-update-v1` sends it as `other`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Let a member's update request replace the automatic schedule
On a hosted server, the automatic schedule waits for client use, also
for the use of the member who asks. Also accept an undefined
`clientInUse` for exactOptionalPropertyTypes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Install OpenBot as a server from a terminal
Add a self-hosted server mode for a Linux computer with no screen.
install-server.sh downloads the latest release, checks it against the
release manifest, and runs the setup file of that release. The setup
uses the install steps of a hosted server, with the mode "self".
Main opens a control socket in the runtime directory of the service
user (0700, socket 0600). The `openbot` command uses it to sign in with
an email code, set the server name, show the status and sign out.
Main checks the server name before it stores it, and the status shows
why a publish failed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Keep the sign-in code out of curl arguments, and keep install values
- The openbot command sends the form body to curl on standard input.
Other local users can read process arguments in /proc.
- A reinstall keeps the installed service user and account server when
the options are not given, and refuses another --user. The keyring
and the sign-in belong to them.
- Setup starts openbot-update.timer, so update checks start before the
first reboot.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>