Maya Editor
A small native macOS editor with a real terminal — and in the same window git, pull requests with review, Kubernetes, databases and an issue board. The things that otherwise send you to another app several times an hour are a tab or a pane here. And Claude Code or Codex runs in that terminal like any other process, with session history and a seat at the review.
Quit the editor, restart the Mac or install an update — and on launch every project is back, tabs in their old order, and every Claude Code or Codex session resumes in its own tab. An agent that is mid-turn is never ended without asking: Interrupt and Quit, or Wait for Them.
A red dot on a terminal tab:
Claude is waiting for your permission. Blue: it finished a turn in a tab you were
not looking at. The project's tab carries the dot too, so you see
it while working somewhere else. Nothing to install — the editor
reads what Claude writes about itself to
~/.claude/sessions, for a claude typed
by hand as well.
A colour and an emoji on the project's tab, in the recent projects
list and on Favorites cards — production never passes for
staging. Eight presets or any colour you like. Stored in
.maya/project.json, so it travels with the
repository and committing it is your call.
Each of these is a tab or a pane in the same window as your files. None of them opens another app, another sign-in or another account.
No chat panel and no API. The agent runs as a process in the same
zsh -l you would have started yourself — only in a
window that also holds the files, the diffs and git. Around that,
the editor does four things.
⇧⌘R opens a tab straight into claude. The folder comes from the project, and the opening message you set is filled in with the project's name. With nothing configured it starts a bare claude and waits.
The arrow beside ✦ lists the project's last eight sessions; ⌥⌘R opens the whole list as a searchable palette. The rows come from the transcripts in ~/.claude/projects — nothing is copied and nothing is sent.
Quit the editor, restart the Mac or install an update, and every project comes back as it was: the same tabs in the same order, and every Claude Code or Codex session that was running back in its own tab. The editor remembers which session was where, so there is nothing to hunt for. Switch it on in Settings.
The editor is an MCP server named maya-editor: the agent gets the pull request's diff, code and threads, and its comments land in a draft that a person reads and submits. The agent never holds a token — the editor talks to GitHub.
LSP, autocomplete, a debugger, extensions, collaboration, remote development, a build system. That is not a list of things not done yet — it is a decision. You already know the editor that does all of it; this one is small on purpose.
Nobody yet. The Company tier on GitHub Sponsors puts a logo and a link right here — where people deciding about the editor will see it.
After downloading you sign in through GitHub and it runs for 30 days. The trial is counted on the server against your GitHub account, so reinstalling will not reset it — and it will not run down before you launch the app either.
It keeps running for anyone sponsoring mesour on GitHub. Private sponsorships work too — the question is asked with your own token.
The app has no password field and must not have one. The whole sign-in runs at GitHub; only a signed licence comes back. What leaves your Mac is written up on one page, with the commands to check it.
A licence is good for a week without a network. It is a deliberate trade: a longer window would mean a cancelled sponsorship taking longer to run out.