The latest articles on DEV Community by mocu (@kharchang_ai_fe9446939ed0). https://dev.to/kharchang_ai_fe9446939ed0 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4226172%2F800fde07-de2b-4fea-9851-4fc87be3c153.png https://dev.to/kharchang_ai_fe9446939ed0 en mocu Wed, 04 Nov 2026 13:14:55 +0000 https://dev.to/kharchang_ai_fe9446939ed0/ive-been-meaning-to-build-my-own-ai-tool-for-five-years-heres-the-alpha-4ijm https://dev.to/kharchang_ai_fe9446939ed0/ive-been-meaning-to-build-my-own-ai-tool-for-five-years-heres-the-alpha-4ijm <p>I'm Maysam. For about five years I've been telling myself I'd build my own AI project "when I had the right idea." Mocu is the first version I actually open every day — and yes, it's alpha, and it shows.</p> <h2> What Mocu actually is </h2> <p>A desktop workspace where you build your own small AI systems around the work you actually do, instead of adopting a generic assistant and bending your workflow around it. It's text-based, and each project keeps its own context and its own folder, so long-running work doesn't restart from zero every time you open a chat.</p> <h2> What you can build with it </h2> <ul> <li> <strong>Agents</strong> — saved assistants with their own instructions and their own chosen set of tools and skills. Not one giant chatbot, but small specialists you can point at one job.</li> <li> <strong>Extensions</strong> — add new capabilities to the workspace. Some of them ship their own HTML interface inside Mocu, so they feel like a small app rather than a command.</li> <li> <strong>Apps</strong> — those in-workspace interfaces. You get an interface built for the task, instead of memorizing commands and hoping you remember the flags next month.</li> </ul> <p>Put together, these let you assemble a setup that's genuinely yours: an agent that knows how <em>your</em> project is organized, extensions that do the specific boring thing you always have to do, and an app surface for the part you touch every day.</p> <h2> Why I built it instead of using what's already out there </h2> <p>My read on where this is going seems a bit different from most tools I try. I don't want agents that do my work <em>for</em> me. I want ones that help me do it — that know my project, keep the context, and point at the next useful step instead of pretending to be me.</p> <p>That's the whole design bet. Mocu is a workbench, not an employee.</p> <h2> The honest part </h2> <p>It's alpha. There are rough edges, some things break, and some parts will change. I've also been using Mocu to help build Mocu, which is a strange and slightly humbling loop — when it fails at my own task, that's usually the next bug to fix.</p> <p>I'd rather show up with something imperfect that I use every day than keep waiting for the version that's ready.</p> <h2> What I'd genuinely like from this community </h2> <p>Try it and tell me where it breaks. Not "nice project" — the actual friction. If you have an idea for a small system you'd want to build for yourself (an agent, an extension, a workflow), tell me that too; it's the most useful input I can get right now. Issues and PRs are very welcome.</p> <p>Repo and setup instructions: <a href="https://github.com/kharchangai/Mocu" rel="noopener noreferrer">https://github.com/kharchangai/Mocu</a></p> <p>One question I'm curious about: what's the one thing you'd want an AI tool to remember about your project so you'd stop re-explaining yourself? I keep changing my answer.</p> showdev ai opensource productivity