Why We Started

We started Nap to make building with coding agents feel straightforward. Open an app, choose a project, and tell an agent what you want to do. Read its response, look at the changes, and decide what happens next. That whole loop belongs in one place.

A native interface gives that work a home: your projects, your conversations, and the changes taking shape around them.

Start with what you want to build.

A session might begin with a bug you can reproduce, a feature you have been thinking about, or a part of the code you want to understand. Nap gives you a place to bring that question to an agent and work through the answer.

You can describe the goal in the conversation, follow the agent’s activity, and review the result. The experience stays inside the app.

Your agents. One familiar app.

You might prefer Claude Code for one task and Codex for another. Nap brings your coding agents into a shared interface, so choosing an agent is part of working on a project.

The surrounding experience should stay familiar: find your project, open a conversation, and get going. Your choice of agent can change while the place you work stays consistent.

Keep the decisions close.

The useful part of a conversation often lives between the prompts. There is the approach you ruled out, the detail you clarified, and the explanation that helped you understand a change. Those things are part of the project too.

Keeping sessions and conversations together makes it easier to return after a break. You can find your thread and continue with the reasoning still close at hand.

Make room for the work.

Our aim is a focused app that helps you move from an idea to a change you understand. You still decide what to ask for, what to keep, and where to go next.

That is the idea behind Nap: your agents, all together, with more room for your own thinking.