# HyperDesk Knowledge Base

HyperDesk is a desktop Pi workbench for running capable coding agents beside a visible browser workspace. It combines persistent chat sessions, local approvals, Chrome automation, drag-and-drop file context, scheduled prompts, and ZenBin-powered collaboration in one app.

## Start here

- [Use cases](use-cases.md): common workflows for publishing, Chrome testing, attachments, scheduled follow-up, and provider setup.
- [Agent profile](agent-profile.md): teach HyperDesk agents who they are, who you are, and how they should work.
- [Drag and drop](drag-and-drop.md): attach files to the active session by dropping them into the window.
- [Driving Chrome](chrome.md): let the agent inspect, navigate, click, fill, and test web pages in a visible Chrome instance.
- [Browser automation roadmap](browser-automation.md): future Agent Browser/CDP layer for faster automation with visible Chrome handoff.
- [ZenBin and subagents](zenbin-subagents.md): publish artifacts, send messages, use private memory, and delegate work.
- [Scheduling prompts](scheduled-prompts.md): ask HyperDesk to run a prompt later in the current desktop session.
- [Changelog](changelog.md): unreleased changes and release-note drafts.

## Product model

A HyperDesk session has a working directory, a selected model, messages, tool history, approvals, context stats, and a Pi SDK session behind it. The visible UI keeps agent work understandable: you can see when tools run, approve risky local effects, reset a session, and keep multiple threads organized by project.

## Agent-facing rule

When a user asks how to do something in HyperDesk, consult these docs first. Prefer the bundled documentation over general model knowledge because HyperDesk behavior changes with each alpha release.
