DeskRPG: A Self-Hosted Pixel-Art Office Where AI NPCs Do Your Bidding

What DeskRPG Actually Solves

DeskRPG is a 2D pixel-art virtual office that you can self-host. It solves a specific problem: making remote collaboration feel less like a list of chat windows and more like a shared physical space. You create an LPC-based character, walk around a live office map, and interact with AI NPCs that are connected to OpenClaw agents. The intended user is someone who wants a playful workspace, not another plain chat room. This is not a general-purpose team chat tool. It is a niche product for teams or hobbyists who want to bring a game-like layer to work coordination. The README positions it as an alternative to the usual text-based collaboration, and it is honest about that scope.

The Architecture: Channels, NPCs, and OpenClaw as the Brain

DeskRPG is built around channels, which are shared office spaces. Each channel has a map from a template, and characters enter that space. The core mechanism is the connection between in-world NPCs and OpenClaw agents. OpenClaw acts as the gateway that provides the AI reasoning. Without it, NPC hiring, task automation, and AI meetings do not work. The data flow is straightforward: you configure an OpenClaw gateway URL and token in the app's channel settings, then bind NPCs to available agents. Tasks move through states (waiting, in progress, stalled, completed) and NPCs can be nudged to continue. Reports are delivered in-world, with the NPC walking over to the player. This is a clever design choice: the AI is not embedded in DeskRPG itself but delegated to an external service. That keeps the core app lighter but introduces a hard dependency.

Six Ways to Start, From npm to Docker Compose

The README offers six setup options. The simplest is the npm runtime: run `npx deskrpg init` and then `npx deskrpg start`. That stores state under `~/.deskrpg/` with a SQLite database by default. For a full repo run, you clone, run `npm install`, copy `.env.example` to `.env.local`, then `npm run setup` (PostgreSQL) or `npm run setup:lite` (SQLite), and finally `npm run dev`. Docker users get three compose files: `docker-compose.yml` for PostgreSQL, `docker-compose.openclaw.yml` for the full stack with OpenClaw, and `docker-compose.lite.yml` for SQLite. Each requires setting `JWT_SECRET` and, in the PostgreSQL cases, `POSTGRES_PASSWORD`. The OpenClaw stack also needs `OPENCLAW_TOKEN`. The port differs: repo dev runs on 3000, Docker on 3102. This variety is useful, but it also means you have to choose carefully based on your database preference and whether you need AI.

The OpenClaw Dependency Is the Real Cost

The biggest limitation is that AI features are not optional extras. They are the heart of the product. The README states that until you complete provider and model onboarding in the OpenClaw dashboard, NPC hiring, task automation, and AI meetings will not work. That means you are not just installing DeskRPG; you are also running and configuring a second system. The integrated Docker stack helps by bundling OpenClaw, but you still have to open the OpenClaw dashboard, set up a provider and model, and then paste the gateway URL and token back into DeskRPG. This is a two-system configuration that can fail at several points. If OpenClaw has an outage or you misconfigure the token, your NPCs become decoration. For a team that just wants a chat tool, this is a heavy prerequisite. The README is transparent about this, but the complexity is real.

Where DeskRPG Is the Wrong Tool

DeskRPG is not a replacement for a serious project management tool. The task board is basic, with states like waiting, in progress, stalled, and completed, but there is no mention of due dates, assignments to human users, or integrations with external trackers. The meetings are AI-driven and channel-scoped, but they depend on OpenClaw and produce notes stored in the header. If you need structured workflows, audit trails, or compliance features, this is not the tool. Also, the map editor is browser-based and supports Tiled-style workflows, but that is a niche skill. For a team that does not want to design maps or manage AI agents, the setup cost outweighs the benefit. The README itself notes that login is required even with an invite code, so it is not an anonymous access tool. That is a deliberate boundary, but it may surprise someone expecting a quick demo.

A Real Alternative: Plain Chat with Bot Integrations

The most direct alternative is a standard team chat platform like Slack or Discord with bot integrations. Those tools give you real-time messaging, file sharing, and a mature ecosystem of bots that can handle tasks and meetings without a pixel-art layer. The difference in approach is fundamental: DeskRPG spatializes collaboration, making presence and movement part of the experience, while chat tools abstract away space entirely. If you want AI assistance, Slack bots or Discord bots can connect to the same OpenClaw or other agent frameworks without requiring a custom map or character creation. The trade-off is that you lose the playful, embodied interaction. DeskRPG is a deliberate choice for that playfulness, but it comes at the cost of complexity and a narrower feature set. For most teams, a chat tool with bots is easier to adopt and maintain.

Maintenance, Upgrades, and License Caveats

The project is under active development, with recent releases in April and May 2026. The npm package is published as `deskrpg`, and Docker images are tagged by version, so you can pin a release by changing `DESKRPG_IMAGE`. That is a good sign for upgrade discipline. However, the license is listed as NOASSERTION, which means the repository does not declare a standard open-source license. That is a serious issue for adoption. You cannot assume you have the right to use, modify, or redistribute the code without explicit permission. The README does not clarify this. Before any production use, you must contact the maintainers to get a clear license. The maintenance cost includes keeping OpenClaw updated and configured, not just DeskRPG itself. The state is stored in SQLite or PostgreSQL, and the npm install path keeps mutable data under `~/.deskrpg/`, which is easy to back up but also easy to lose if you forget it exists.

Editorial conclusion

Adopt DeskRPG if you want a playful, self-hosted workspace and are willing to manage an OpenClaw gateway for any AI feature to work. Skip it if you need a production-grade collaboration tool or if you cannot accept the NOASSERTION license. Before adopting, verify the license status with the maintainers, test the OpenClaw integration end to end, and confirm that the browser-based map editor and task board meet your workflow needs. The project is actively developed, but its AI core is only as reliable as the OpenClaw setup you configure.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes