Get started

Help

Ask Jevie how to do anything in Jevie and get the answer as you type, with sentences to try right under it.

FreeMac

Choose an example to copy it, then try it in Jevie.

Use itHow it worksLimitsWhere it's kept

Use it

• helpAs you type: what can be asked, then everything Jevie does
• what can you dowhat can i do hereEverything Jevie can do in one list: its overview by section, then every area, what fits the screen first; ↵ puts a sentence in the field to try
• everything jevie can doEvery area, each with sentences that work
• help tilinghelp snippetsThat area's guide, live, as you type
• how do i do layoutsThe sentences you need, grouped by what they do
• explain triggershow does dictation work in jevieExplained from the docs, with sentences to try
• can jevie fill out a pdfdoes jevie work offlineAny question about Jevie, plans and privacy included
• type help, then TabLocked to Help: anything you ask is about Jevie
• copy debug infoA plain-text report for a bug report, on the clipboard: versions, this Mac, the look, the phone, linked computers and team Macs, coding agents, the Chrome extension and what doctor finds missing; also Copy Debug Info in Jev's menu
• copy version infojevie versionThe short form: Jevie's version, build and commit, the daemon, macOS and the Mac's model

How it works

Every part of Jevie has a guide, and Help answers from those guides alone, naming the ones it read. Press ↵ on a sentence in a guide to put it in the field to try or change; nothing runs unasked.

What fits the screen comes first: with a web page in front, what you can do on the page leads.

People who use Jevie are a good second answer: news, tips and short clips of what Jevie can do are on X at @heyjevie, and the links at the foot of every docs page lead to where people meet.

Bugs and ideas reach the team fastest with what you said, what you expected and what happened; saying doctor first and including what it names helps more. Copy debug info puts all of that on the clipboard in one go, made in code from what Jevie already knows, with no model asked. It says versions, states and counts only: never a key, a token, an email, a file's contents, a name, or a path past ~, and a theme made from your own words is words of your own.

Linked computers and team Macs are numbered (PC 1, Mac 2), not named.

Limits

• An explanation is only as complete as the docs; what they don't say, it says it doesn't know.
• An explanation needs a model; the guides and their sentences do not.
• how do I cook rice names nothing of Jevie's, so it goes to the web.
• Debug info runs the doctor, so it takes a few seconds; the version info does not. A team Mac's version is not told yet, only whether it answers; a linked computer tells the API revision it speaks.

Where it's kept

docs/guide/*.md (one per concept) and each surface's own description.

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

Related

Updated 30 October 2026 · Something wrong or missing? Tell us