| name | code-os |
| description | Operate and verify Code OS dashboards, projects, Portly apps, Git state, screenshots, login sessions, and media bypass URLs on local or VPS development environments. |
Code OS
Use the local Code OS CLI and configuration as the source of truth.
Inspect
- Run
code-os doctor.
- Read
~/.config/code-os/config.json for the loopback address, dashboard hostname, and credential file paths.
- Run
code-os status for a summary or code-os scan for the current snapshot.
- Inspect the user service with
systemctl --user status code-os.service on Linux.
Keep Git inspection read-only. Use Portly for persistent development processes.
Authenticate the dashboard
Open https://<dashboardHost>/login. The form uses standard username and current-password autocomplete fields, so use the configured username and the password stored at auth.passwordFile.
Never print, commit, or paste the password file contents.
Publish and embed private visual evidence
Use a media-only bypass URL when Cursor, Codex, or another image client cannot keep the dashboard session:
https://<dashboardHost>/media/<screenshot-id>?bp=<url-encoded-bypass-key>
For a new verification artifact, write it beneath the configured filesRoot using a feature directory and a stable evidence filename, then use:
https://<dashboardHost>/files/<feature>/<evidence>.png?bp=<url-encoded-bypass-key>
- Obtain the screenshot ID from an authenticated
/api/snapshot.
- Read the key path from
auth.bypassKeyFile; consume its contents without printing them.
