Open Cursor or a cloud IDE and you're still in a code editor first. The AI assists inside that frame. That works brilliantly for engineers who live in diffs and file trees.
Our users are different. They know enough web coding to direct work, but they'd rather say what they want than navigate a repository.
Conversation as the primary interface
In My AI Weapon, the chat thread is home base. You describe outcomes — build this page, fix that endpoint, search competitors and summarize — and the agent plans steps, writes files, runs commands, and reports back in the same thread.
Progress is visible as a narrative: planning, writing, running, reviewing. You're not hunting through panels to learn what happened.
When editor-first still wins
We're honest about the tradeoff. If you want pixel-level control of every line, a traditional IDE may fit better. We're not trying to replace that workflow.
We're building for builders who treat code as a means to an end: landing pages, internal tools, automations, small products. The interface matches that intent.
Less context switching, more completion
Editor-first tools scatter context across tabs, terminals, and chat history. Chat-first keeps the request, the plan, and the result in one scrollable story.
That's especially important on a laptop in a coffee shop or on a tablet between meetings — devices where a full IDE chrome feels heavy anyway.