Hi everyone! ![]()
I’d like to share something I’ve been building with Frappe and using it in production developments: Atlas.
While working on Frappe projects, we often switch between our editor, servers, AI chats, documentation and project notes. We wanted to bring more of that workflow together inside the familiar Frappe Desk.
Atlas is built primarily for developers, while keeping everyday tasks approachable through conversation.
Here’s what it brings together:
-
Chat: discuss requirements, explore code, build pages and preview the results.
-
Projects and servers: connect development workspaces and keep related conversations and project context together.
-
Coding tool integration: give tools such as Codex and Cursor access to project knowledge, source search, skills and memory through MCP.
-
Bots and recurring duties: create a bot through chat, explain its responsibilities and schedule recurring work.
-
Skills, plugins and memory: add reusable guidance and retain useful knowledge for future tasks.
-
Frappe / ERPNext connections: work with connected site records using the account’s permissions.
-
Models: I’m a big fan of local model, i have a DGX Spark, i’m hosting Qwen3.8 Flash Next into it and the whole atlas app is build with the help of this model. but you can register a cloud model too.
I’ve attached a walkthrough showing the actual interface, including building a landing-page preview and creating a bot with a recurring duty through chat. Long waiting periods are cut to keep it watchable.
It’s still evolving, and I’d love to hear what fellow Frappe developers think. Which parts would be useful in your workflow, and what would you approach differently?
Thanks for taking a look!





