Your browser

Jevie Browser

Keep hundreds of pages open as tiles beside your terminals, already signed in with your Chrome logins, and watch agents work in them.

FreeMacLinuxPhone

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

Use itHow it worksLimitsWhere it's kept

Use it

Pages as tiles

• open github.comopen the top 3 hacker news storiesOpens on the wall, signed in where your Chrome is
• open github.com on the wallOn the wall even while Chrome is in front
• A new tab (⌘T, + or new tab) is drawn in your look, never a white page: a large field in its middle lists the sites you go to most before you type, ↑ ↓ choose one and Return opens it
• … in chromeAnywhere in the sentence, that page or errand goes to your Chrome instead

In the palette

• type chicken recipeAsk Google (Google's AI answer) and, right under it, Search Google (Google's plain results, no AI answer) come first; google notch or notch on google asks and searches Google for notch. Ask Google comes first, or right under the app the words name and its own rows (obs: OBS, Uninstall OBS, then Ask Google). ↵ still runs what Jevie decides; go to Ask Google and ↵ to ask it. While Google works the palette thinks as it does for its own answers (the words shimmer, the rim lights); then Google's AI answer (AI Mode) is shown in the palette as Google drew it, its pictures and cards kept, without its rail, bars or ask box (from its first word, and for every follow-up), centred, in your look's light or dark, its grey cards and buttons as faint films over the palette's colour, and the palette grows to the screen's height for it and for every follow-up, at the same width wherever you ask (on the wall or over any app). When the answer has finished writing, a soft band of light passes up it once (Claude's reply opened in the palette gets the same), never while it loads and never over an error; Reduce Motion, or defaults write ai.jevie.jevie answerSweep -bool false, turns it off. Type a follow-up in the palette's field and ↵ asks Google in the same conversation; Esc goes back to the list; closing the palette keeps the last answer, and the next ⌘Space opens on it, ⌘↩ puts Google's page on the wall. A link in the answer (a source, a video) opens over it in the palette's own browser, the page alone with its address in the field; Esc goes back to the answer, ⌘↩ puts the page on the wall. On the phone the launcher's Ask Google opens the same AI answer through the Mac's own browser. Google's completions follow when Google suggestions are on, each its own answer; with them on, the answer starts loading while you pause
• a site and a time in the wordsGithub month swift, reddit week ai, hn month rust, google week notch — the site's own filtered search heads the list (Search), opened in the palette (every search and quicklink search opens in Jevie's own browser, never a Chrome tab); github swift also offers its past week and past month
• every match on your Mac still follows Google's rows, files included, the same list on the Mac and in the phone's launcher
• a page opened in the palette (Search Google's results, a site's search, a link) takes the keys, not the field: browse it with the wall's keys straight away (j k to scroll, gg G, ⌃d ⌃u, f to follow a link, H L back and forward, / to find); Esc leaves a field on the page first, then goes back to the list
• a web answer grows the palette down to most of the screen, so it reads as a page
• google pizza doughsearch the web for sourdough starterThe results page in the palette itself, in place of the list
• type any words and ⌥↩Their plain results page there at once, no sentence read
• EscBack to the list (the page closes; ⇧⌘T on the wall brings it back) · ⌘↩ — the same page, as it is, onto the wall as a tile · ⌘[ ⌘] — back and forward · typing new words — back to the list for them

From your phone

• Work → Browser → Open: type an address or words to search; the pages you have open and the places you have been (on the wall and in Chrome) are listed as you type
• The globe under Work's list counts what is open: the wall's pages and the Chrome tabs an agent drives (Claude or Codex over Jevie's browser tools). It turns yellow when one of those tabs waits at a sign-in, and the accent colour while one is at work. Tap it to see them before typing anything
• A session stopped at a sign-in in Chrome says so on its row: Sign in to apple.com in Chrome · waiting for you.
• Tap a tab in the list to watch it live and tap, scroll and type in it, a Chrome tab an agent drives included (only those, never your other Chrome tabs). The page fills the phone, as your Mac's whole screen does: × to close and where it is at the top (tap it for another address; the pages you have been to are offered as you type), and one bar at the bottom with back, forward, keyboard and reload, plus the page's own buttons only when it needs them (Sign in on an errand's page, phone or Mac layout, zoom). The bar turns dark over a dark page and light over a light one. A Chrome tab that Chrome put to sleep in the background is woken first. Its × in the list closes it; held down, several are picked and closed together. A password is never typed into the page from the phone's keyboard: use Sign in below
• The page is sent to the phone the moment it changes, not asked for again and again, so a page you act in answers at once and a still one costs nothing
• What your finger will press lights up as it lands. A tap that just misses a link or button presses the one you meant. A tap is a real click on your Mac, so sites that ignore a script's click, pop-ups and hover menus answer it
• A page you watch on the phone is your site's phone version (Jevie asks for it as an iPhone's Safari does), and the Mac's version again with the phone or Mac layout button. An agent's page keeps the Mac's version, so its work does not change under it
• Tap a field and type where it is, with your phone's own keyboard, starting from the words already in it; Return sends it. The keyboard does not shrink the page: it scrolls to keep the field in sight. A list to pick from (a drop-down) opens as a list on your phone. Touch and hold a link to open it, open it as a new page or copy its address
• Drag to scroll: the page moves under your finger at once. Pull down at the top to reload. Swipe a long way sideways to go back or forward. The keyboard button in the bar types into whatever has focus, for a page whose field Jevie cannot see
• When an errand stops at a sign-in, your phone is told (Sign in to doordash.com), and the chip over the field says Sign in. Tap either: the page opens with fields of the phone's own, so your phone's password manager can fill them. Jevie types them into that page on your Mac and sends it, one step at a time (the name, then the password, then a code), and says Signed in or the site's own words, such as Wrong password. The lock at the top of a watched page opens the same sign-in any time
• While Jevie works in a page, the chip over the field says the step it is on (Comparing 3-bed flats in Alfama); tap Watch to see the page itself
• jevie://onboarding typed there runs the first run on the phone; the row under it, On your Mac, shown here, runs the Mac's instead and shows its screen on the phone. A step only the Mac has (jevie://onboarding?page=signins) opens there. jevie://settings and jevie://appearance open the phone's own; jevie://sounds, setup and dials are the Mac's

Your sign-ins

• Use my Brave sign-insOn first run, your browser's sign-ins come over at once
• with my Brave logins on the wall… with my Chrome loginsChoose whose sign-ins the wall uses

Agents at work

• find a usb-c hub under $80 on amazonThe agent works in its own tile you can watch, zoom into and take over
• file each of my X bookmarks into a folderDone by hand once, then repeated over the rest in seconds each

Keys on a page

Vim keys, as qutebrowser, Vimium and Surfingkeys have them. They never act while you type in a field: Esc leaves the field first. ? on a page lists them all.

• j k · h lScroll down, up, left, right; d u (or ⌃D ⌃U) half a page; gg G the top and the bottom; a number first repeats (5j)
• fA letter on every link and button; type it to follow. C opens it in a tab behind, af in a tab in front, yf copies its address
• giThe first text field; ] [ the next and previous page of a list
• S D (or H L)Back and forward; r reload; gu up a folder, gU the site's root
• zi zo zz (or + - =)Zoom in, out, back to normal
• R E (or J K, gt gT)The next and previous tab; g0 g$ the first and last; T choose a tab, the last used first; B F back and forward through the tabs in the order you used them
• tA new tab; go edit this address; x close the tab, X bring the last one back
• /Find on the page, n N the next and previous match
• yyCopy the address; p opens the copied address or words here, P in a new tab
• iEvery key goes to the page until Esc, for a site with keys of its own

The command bar

: on a page (or go to start from the address). Type an address, a site, or words to search; or a command:

As you type an address or words, the pages you have open and the places you have been that hold them are listed under the bar, the likeliest first. ⌘J ⌘K (or ↑ ↓) choose one and Return opens it; one already open is gone to instead of opened again. Return with none chosen opens what you typed. Jevie's own links, such as jevie://onboarding, open in Jevie as they do from Chrome.

• :open :o an address here · :tabopen :t in a new tab
• :back · :forward · :reload
• :close :q the tab · :undo :u bring the last closed back
• :zoom 125 (a percent; :zoom alone resets) · :find words · :yank copy the address
• :chrome · Keep the page in Chrome instead: it opens there and leaves the wall
• :help · Every key

The page's tile

The wall's own keys on the page in hand, as in Safari and Chrome:

• ⌘DType another address (⌘L is the wall's move right)
• ⌘TA new tab · ⌘⇧T — the last closed tab back · ⌘W — close
• ⌘FFind · ⌘R — reload · ⌘⌥[ ⌘⌥] — back and forward
• ⌘[ ⌘]The tile's tabs, as on every tile
• ⌘PKeep the page in Chrome
• An agent at work in the tile: ⌘⇧O takes over and hands back, ⌘. stops it

How it works

Every page is a tile in Jevie Studio, beside your terminals. Only the pages you can see or an agent is using stay live; the rest sleep as a picture and wake when shown, so hundreds can stay open. Vim-style keys, link hints and a command bar work on every page, and Jevie Browser can be your default browser.

Your Chrome cookies come over so you are already signed in (and signing out in Chrome signs Jevie Browser out too, within ten minutes), and saved logins and autofill are filled in for you without a password ever reaching a model. A repetitive errand is turned into a small program after the first item and run over the rest with no model call between them. Anything that pays, orders, books, subscribes, sends or posts in your name, deletes, cancels or changes your account stays yours.

An ordinary form's Submit, Confirm or Sign up goes ahead.

When an agent's page asks you to sign in, the tile comes to the front and Jevie says so. Nothing runs while you sign in: the errand is saved, and it carries on from where it stopped once the page lets you in, even if Jevie restarted meanwhile. If you don't sign in within 10 minutes or close the tab, the errand stops and says so.

Limits

• It is Safari's engine, not Chrome: a few sites refuse it and Chrome extensions do not run.
• Passkeys are not offered yet: Jevie Browser tells sites it has none, so Google and others ask for your password or a prompt on your phone instead of a passkey that would fail. A sign-in tied to Chrome's device needs one sign-in on the wall.
• Reading Chrome's logins needs your Always Allow once. Jevie then keeps its own copy of Chrome's key in your Keychain, readable only by Jevie, so your sign-ins keep coming over even if Chrome's permission is later lost. If they stop, Jevie says so once, and use my Chrome logins on the wall asks again. The first time a page wants a Chrome sign-in, Jevie says why before macOS asks; the first run no longer asks. A checkout inside Jevie never asks: with the permission, Stripe Link knows you as it does in Chrome; without it, the checkout opens in Chrome, where Link already knows you.
• On a Mac, Chrome's key never leaves the Jevie app: the app decrypts your cookies and saved passwords itself, and nothing else on the Mac, Jevie's own background process included, ever gets the key, a cookie's value or a password.
• Chrome's cookies are kept by Jevie Browser once they come over, sealed in its own encrypted file, so Jevie Browser stays signed in even when Chrome's permission is lost (as after Jevie updates itself); they are refreshed from Chrome whenever Jevie may read its key. The file's key is in your Keychain where other programs you run could ask for it, as Jevie's API keys are. Sign-ins you make on the wall itself are kept too.
• An agent never carries your name, email or phone number to another site, and uploads only your own documents.
• A sign-in from the phone is typed into the page and not kept: not on the phone, not on the Mac, not in any record. Jevie hears only whether you got in. Your phone's password manager offers what it has saved for the site, if it has anything.
• A page with a card's number or security code typed in is not shown on the phone while it holds them.
• An agent opens a page on your own network (your router, a printer, a NAS) only when your request names it, as in open my router at 192.168.1.1. A page cannot send it there, by a link, a redirect or its text.
• A server on this Mac (a dev server, Ollama, a notebook) opens for an agent only when your request names its port, as in check localhost:5173. A page cannot send it there either.

Where it's kept

~/.jevie/browser/.

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

Related

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