See which sessions need an answer

Choose which visible sessions add attention markers: questions, permission requests, idle agents or exhausted quota. Projects shows the count; each group shows a hand. Hidden sessions stay excluded.

How it works

  1. Projects

    Browse repositories, containers and retained sessions. Native tool waits differ from questions, permissions and provider errors; a ready prompt alone is not a blocker.

  2. Configure project workflows

    Choose delegated tasks, required code review, tracker work or diagnostics. The same controller operations are available through CLI and scoped MCP tools.

  3. Set explicit execution limits

    Choose allowed accounts and hosts, concurrency and budgets before starting work. The demo opens the real form but does not save permissions or launch agents.

  4. Inspect the daily skill catalog

    The published catalog refreshes every 24 hours, separately from optional ⁠GitHub discovery. This synthetic outage keeps cached metadata visible; it neither fetches a bundle nor changes pinned assignments.

  5. Keep discovery metadata separate

    A metadata digest does not verify skill contents, runtime compatibility or execution. Fetch and verify a complete bundle before installation, binding or review pinning.

  6. Choose skills from manifest evidence

    The real Recommended skills panel matches a synthetic React/Nest manifest against maintained JSON mappings. Source links, package fields and installation status remain visible.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

Watch the workflow

ProjectsREAL UI

Loading the recorded terminal…

Walkthrough paused

Release videos

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.