Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
A self-hosted 2D AI workspace for AI Agents
| Date | Stars |
|---|---|
| 2026-07-31 | 306 |
| 2026-08-06 | 306 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
35.0
growth rate 0.00%/day
# My Virtual Office 🌐 **[myvirtualoffice.ai](https://myvirtualoffice.ai/)** A self-hosted 2D AI workspace for AI Agents. Turn invisible agent work into a living, breathing office.  ## What Is It? Virtual Office gives your AI agents a physical presence. Instead of watching logs scroll by, you see agents walking between desks, grabbing coffee, sitting in meetings, and chatting in a charming 2D style office that runs in your browser. It connects to supported agent harnesses and visualizes what your agents are doing in real time. ## Supported Agent Harnesses ### OpenClaw Virtual Office connects to OpenClaw through the OpenClaw gateway and the mounted OpenClaw home directory. The gateway provides live chat and activity events, while the home directory lets Virtual Office discover agents, read safe profile metadata, load model settings, and surface workspace tools in the UI. For Docker deployments, mount your OpenClaw home directory into the container and set `VO_OPENCLAW_PATH`, `VO_GATEWAY_URL`, and `VO_GATEWAY_HTTP` when the defaults do not match your setup. ### Hermes Agents Virtual Office connects to Hermes as an external client of Hermes' authenticated API Server. Hermes itself owns each profile, gateway process, tools, sessions, credentials, model configuration, and terminal environment. Virtual Office uses `/v1/runs`, SSE events, approvals, stops, and the documented session API; it never starts Hermes or runs the Hermes CLI inside the Virtual Office container. Run one native Hermes gateway per profile and add one connection per gateway in **Settings → Integrations → Hermes**. Each connection has a stable ID, display name, API URL, and `API_SERVER_KEY`. Docker deployments commonly use `http://host.docker.internal:<port>`; host-network deployments can use `http://127.0.0.1:<port>`. You may also supply the repeatable connection list through `VO_HERMES_CONNECTIONS_JSON`. Do not mount the Hermes home directory or CLI into Virtual Office. Virtual Office also ships a Hermes Messaging Gateway platform plugin under `integrations/hermes-platform/my_virtual_office/`. This is a different mode: Hermes gateway connects to Virtual Office as a messaging platform, so the `Hermes Gateway` office agent can receive queued Virtual Office messages and post replies back into visible office chat. Configure `VO_HERMES_PLATFORM_TOKEN` on Virtual Office, copy the plugin into `~/.hermes/plugins/my_virtual_office/`, set `MY_VIRTUAL_OFFICE_URL` and `MY_VIRTUAL_OFFICE_TOKEN` for Hermes, then run `hermes gateway`. ### Codex Virtual Office can create Codex-backed office agents when the Codex CLI is available to the app. Chat uses Codex's native `codex app-server` JSON-RPC protocol for thread start/resume, live progress, approval requests, and interrupt support. `codex exec` is retained only as an explicit compatibility fallback. Discovery includes Virtual Office-created Codex agents, Codex's standard `$CODEX_HOME/agents/*.toml` custom agents, and a synthesized `Main` entry for the default Codex root agent. Newly created Virtual Office Codex agents can use the default Codex agents directory or a custom parent directory. Default-directory creation registers a native custom-agent TOML file under `$CODEX_HOME/agents` when `VO_CODEX_REGISTER_NATIVE_AGENTS=1`; custom-directory creation writes a project-local `.codex/agents/<profile>.toml` and keeps a small Virtual Office registry so the agent remains discoverable. For Docker deployments, install Codex inside the container image or set `VO_CODEX_BIN` to a Codex executable path available inside the container. Set `VO_CODEX_HOME` to a deployment-specific Codex home so auth and config stay out of the repo and are not tied to any developer's machine. Useful variables: `VO_CODEX_BIN`, `VO_CODEX_HOME`, `VO_CODEX_WORKSPACE_ROOT`, `VO_CODEX_MAIN_WORKSPACE`, `VO_CODEX_INCLUDE_MAIN`, `VO_CODEX_INCLUDE_NATIVE_AGENTS`, `VO_CODEX_REGISTER_NATIVE_AGENTS`, `VO_CODEX_PREFER_AP
Excerpt of 15,407 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:a8d953ddb7c92b0d, topic:ai-agents, desc:ai agents