PUBLIC MARKETING + DOCS · HTTPS VERIFIED. The service API, Player, release hosts, protected content delivery, and full production stack remain undeployed and unverified; npm packages remain unpublished.
u1 · product contract
ScreenRig is an agent-operated digital-signage service: an agent uses the CLI and REST API to upload content, assemble a looping playlist, pair a browser screen, and observe the result.
working Build from this checkout; no ScreenRig npm package is published.
# Build the source-checkout CLI
npm --prefix packages/sdk ci
npm --prefix packages/sdk run build
npm --prefix packages/cli ci
npm --prefix packages/cli run sync:sdk
npm --prefix packages/cli run build
# Start the private local stack
make local-up
make smoke
# Initialize and authenticate
screenrig() { node packages/cli/dist/bin.js "$@"; }
screenrig --api-url http://api.screenrig.localhost:8088 \
account create --email agent-owner@example.com --json
screenrig auth status --json
# Open http://play.screenrig.localhost:8088, then claim its code
screenrig screen pair --code ABCDEF --label "Lobby" --json
# Package, upload, and wait for publication
screenrig app upload ./path/to/built-webapp --jsonExpected: account and auth checks succeed; pairing returns a screen; upload waits for a terminal publication operation. ABCDEF and the directory are placeholders. Never paste credentials or live pairing codes into logs.
u2 · decision record
Three interchangeable Go replicas, private storage, workers, CLI, SDK, responsive Player, OpenAPI, pairing, protected content, K/V, operations, and durable events. Optional Android standard/managed/Amazon source and its native content contract are build-tested.
Source checkout only.
CLI-to-REST control, browser Player pairing, responsive playlist pages, and structured observation. Server-published design limits are 50 screens and 1 GiB retained uploads per account.
MCP, billing or payments, screenshot capture, email recovery, and management dashboard are deferred. Android hardware/store validation and a general offline-playback guarantee remain unproven.
u3 · agent workflow
Read llms.txt, load the downloadable skill, then use the generated API reference or raw OpenAPI contract.
Provide an already-built static directory. ScreenRig validates and extracts it; the service does not build or execute uploaded source.
Upload returns durable work. Pin immutable ready application releases and media into a playlist; publication never silently changes a screen.
Open the browser Player, claim its six-character code, then assign the playlist with the screen's current revision.
Follow durable events and operations. Treat cursors as opaque and branch on RFC 9457 problem status and code. Screenshot capture is not part of v1.
u4 · trust boundary
Account bearer tokens stay with the CLI and account API. Uploaded applications run on isolated release origins. Public screen URLs are unlisted read-only playback, not confidentiality; anyone allowed to view a screen can inspect bytes delivered to that browser.
u5 · discovery
u6 · explicit boundary
| Capability | Status | Current boundary |
|---|---|---|
| MCP | later | CLI and REST are the v1 control surfaces. |
| Billing / payments | later | Quota counters are not a financial ledger. |
| Screenshots | later | Use manifests, operations, events, and reports. |
| Email recovery | later | Email is not verified and is not a recovery factor. |
| Management dashboard | later | Agents operate through the CLI/API. |
| Android container | source verified | Standard/managed/Amazon build matrices pass; no KVM instrumentation, physical device validation, or store publication. |
| Offline guarantee | unproven | Native app-private caching and last-known-good retention are implemented, not a general hardware promise. |