Skip to main content
Deployed as a tenant of the Hill90 homelab — hill90.com serves the UI, and identity comes from the homelab’s Keycloak at auth.hill90.com, realm platform. Verified 2026-08-06 07:45 UTC: 23 containers running, 0 unhealthy — the homelab’s 16 and the application’s 7.Identity and data are the platform’s. The tenant’s databases sit on the homelab’s Postgres under a dedicated non-superuser role, and app-auth.hill90.com is not a live surface — it returns 404. Authorization uses client roles on the hill90-ui client rather than realm roles, so holding a homelab realm role does not by itself grant access to the application. A local stack runs its own Postgres, and --standalone its own Keycloak, so pages describing those locally remain accurate.Signing in was completed on 2026-07-30, reported by the operator who performed it. That is not independently re-verified here: realm platform has event storage disabled, so there is no server-side record left to read.Where a page in this section disagrees with AI Application, the overview is newer.

Browser Viewer

The Browser Viewer is a browser-in-browser pane embedded in the Chat page’s session panel. It renders live screenshots from a Playwright Chromium instance running inside the agent container, giving real-time visibility into what an agent sees and does on the web.

Interaction Modes

Take Control

Direct interaction with the remote browser. All input is forwarded to the Playwright instance:
  • Click — click through to elements on the page.
  • Scroll — mouse wheel events forwarded as-is.
  • Keyboard — keystrokes sent directly to Playwright.

Describe

Guided interaction for instructing the agent about a specific element:
  1. Click an element to select it.
  2. A floating popover appears showing element details (tag, id, classes, CSS selector, raw HTML).
  3. Type a natural-language description of what the agent should do with that element.
  4. Send the description to the chat thread for the agent to act on.

Screenshot Refresh

Screenshots refresh automatically after every action (click, navigate, scroll, keypress, type). No manual refresh is required.

Proxy Chain

All interactions are proxied through the full service stack:
The UI never communicates directly with the agent container.

Agentbox Endpoints