Make it yours

Improve Jevie

Type how Jevie should be different and press return: it becomes a rule, a routine, an extension, or a change to Jevie's own code, whichever is the smallest that grants it. Every wish can be taken back.

FreeMacCoding agent

Use itHow it worksLimitsWhere it's kept

Use it

• improve jevie: always use Kagi instead of GoogleKept as a standing rule straight away
• improve jevie: when I say zen, mute the sound and quit SlackA routine you can say from then on
• improve jevie: make me an extension that shows my GitHub notificationsYour coding agent writes an extension, Jevie checks it, you install it
• jevie should show the battery in the paletteA change to Jevie's own code, built on a branch of its own and tested
• i wish jevie would remember my last folderwish: a bigger font in the paletteThe same, said another way
• my wishesEvery wish, where it landed and how it is going
• undo wish 1a2b3c4dThat wish taken back
• let my wishes merge themselvesstop merging my wishesWhether a wish whose code passed its test goes in without asking

How it works

As you type a wish, a card under the field shows it and where it will most likely land. Return sends it.

Jevie tries the smallest change first. A wish already worded as a rule (always …, never …), a name (my wiki is …), a routine (when I say …) or an extension (make me an extension that …) goes straight to that, decided in code. Anything else is placed by one model call, and the result is checked in code: when the smaller change does not really hold the wish, it goes to Jevie's code instead of a guess.

A wish only code can grant becomes an improvement card. Your coding agent builds it on a branch of its own, with a test written first, and the improvement loop judges it the way it judges every card. A wish about how something looks waits for your look. You are notified when it is judged. Say merge card <id> to take it, or let wishes merge themselves. Then a change to Jevie's daemon goes live at once, and a change to the Mac app waits for its next build.

What was in front when you wished (the app, what was in focus, what you asked last) goes with the wish, so this means what it meant then.

Limits

• Code wishes need a coding agent, and a working copy of Jevie's code to build in. A downloaded Jevie grants rules, names, routines and extensions.
• Nothing is merged without your say, unless you said wishes may merge themselves; even then, never over your own work in progress.
• A merged code wish is taken back with git, not undo wish.
• A rule or a name is undone only while it is your newest change to Jevie's files; after that, edit RULES.md or say undo that for the newest.
• Extensions install only when you say so.

Where it's kept

Wishes are kept in ~/.jevie/wishes.json; rules and names in ~/.jevie/self; extension drafts in ~/.jevie/extension-drafts; code wishes as improvement cards in ~/.jevie/improve/cards.json, built in ~/.jevie/worktrees/improve-<id> on the branch improve/<id>.

In Jevie, help improve jevie answers from this page as you type.

Related

Updated 2 November 2026 · Something wrong or missing? Tell us