Questions, answered.

A desktop app that puts chat, projects and a coding agent in one window. It is built for people who use AI every day and want control over how it behaves, without side questions derailing the work in front of them.

Mosaik's word for a project of any kind: a book, an app, a workshop, a hobby. A mosaic keeps a brief, goals, open tasks and memory, and carries them into every conversation inside it. Writing, Research, Art and Code are tabs inside a mosaic, so the work for one project stays together.

Select words in any message and press Ctrl Shift K to ask about them in a popover beside the chat. The answer knows the conversation but is never added to it, so your main thread stays where you left it.

A desktop app. Your conversations and projects live on your own computer, not in a browser tab or on our servers.

Mosaik is developed on Windows first, and its test suite also runs on Linux. Confirm the platforms and minimum versions supported at launch.

Yes. Mosaik was called OpenRouter Chat. On first launch it copies (never moves) your old chats, projects and settings into Mosaik's own folder and leaves the old one exactly as it was, and a remembered API key moves across with it.

Any model available on OpenRouter. You pick a default model, and can override it for a single chat, a project or a coding tier.

Yes. Mosaik reaches models through your own OpenRouter API key, so you are never locked to one vendor. You paste the key once, test the connection, and save it.

Pricing for Mosaik itself is to be announced. Model usage is billed by OpenRouter to your own account, at OpenRouter's prices.

Mosaik shows what each turn cost as you go, and how full the context is. A crew's plan shows its spending cap before you approve it, and research reports show the model and the cost of each question.

Yes. That is one of the two reasons Mosaik exists. Set the model, system prompt, temperature and output limit for the whole app, and override any of them for one conversation. Your instructions win over Mosaik's own guidance.

On your computer. Conversations, projects and settings are kept in a local database in your application-data folder.

In your operating system's credential store, if you choose to remember it, or only for the current session if you don't. It is never written to logs.

Your prompts go to the model provider you chose, through OpenRouter. Web searches go to the search services that answer them, and pages the app reads are fetched from their sites. See our privacy notice for what this website collects.

The agent edits your files directly and runs commands in your project. It is not an operating-system sandbox, so Mosaik gives you three safety nets: a command policy (read-only and test commands run, installs and deletes ask first, destructive commands are refused), a checkpoint for every turn that can be undone, and plans that wait for your approval.

No. Checkpoints work with or without git. In a git repository, each session also works on a branch of its own that you merge back or throw away, and your own uncommitted changes are never committed or switched.

Yes. Each mosaic has rules the agent follows, and it also reads AGENTS.md, CLAUDE.md and similar files. Commands in a project's .mosaik/commands or .claude/commands folder become slash commands.

Early access opens in small waves. Everyone on the waitlist hears from us in the order they joined. Join the waitlist.

Only send you your invitation and the occasional note about Mosaik's launch. We don't share it, and you can ask to be removed at any time.

Write to us from the address you signed up with (see Contact) and we'll remove it.