Your AI assistant and orchestrator.

You are: AI developers who already pay for Claude Code or Codex and keep several projects going at once on one machine, usually alone or in a team of two or three.

The problem: Your day is terminal tabs: one agent per project, dev servers left running, and the same context re-explained every time you switch.

• Hand a task to Claude Code or Codex and keep talking; two jobs run in the background at once.
• A live strip shows what each agent is doing (“Editing page.tsx”) and Neko tells you when it's done.
• Start, stop, restart and open any app in your Apps folder without a terminal.
• “Commit and push” goes to the coding agent, with force pushes always refused.

› “Hey Neko, add dark mode to @awefolio, then commit and push it.”

You are: Independent technical and AI consultants running three to six client engagements at the same time, each with its own codebase, vocabulary and rules.

The problem: Every client lives in a different head-space, and a general-purpose chatbot happily mixes them up.

• A memory group per client: “switch to Acme mode” uses only Acme's memories plus your global ones.
• Load a client's style guide or spec into its group as Knowledge (txt, md, PDF, Word).
• Every client codebase sits inside one Apps folder that Neko's own code won't let it leave.
• Dictate notes after a call: transcribed on your machine and copied to your clipboard.

› “Hey Neko, switch to Acme mode. What did we decide about the billing export?”

You are: Growth and content marketers on small teams who build their own landing pages, microsites and campaign tools with AI, and would rather not live in a terminal.

The problem: AI can write the page, but getting it built, running and published still means asking an engineer for help.

• “Create an app called Spring Launch”: Neko makes the project and a coding agent builds it.
• Keep each brand's voice and guidelines in its own memory group.
• Neko starts the app and opens it in its own window, so you review it the way a visitor will.
• Publish changes by asking: “commit and push spring launch”.

› “Hey Neko, create an app called Spring Launch: a one-page waitlist in our brand colours.”

You are: Product managers and product-minded founders who test an idea with a working prototype before writing the ticket.

The problem: The prototype waits behind the sprint, and your best thinking is scattered across chats, docs and sticky notes.

• Describe the prototype out loud; a coding agent builds it while you keep working.
• A built-in task outline with Today, This Week, Waiting, Back Burner and Goals, which you can fill by voice.
• “Start recording” captures a brainstorm; the transcript lands on your clipboard.
• Mention an app with @ when typing, so Neko knows exactly which prototype you mean.

› “Hey Neko, add “interview three churned users” to this week.”