Artemis: understand a web application by using it

The browser is genuine. The website runs as a native page in a window Artemis owns, so sign-in, multi-factor prompts and the site’s own dialogs behave as they do in Chrome; nothing rewrites its headers or cookies. A bug a reviewer finds must be the site’s, never the tool’s. The console is a transparent layer over that window: an address strip, floating panels, a command card of nine keys, and sound.

The Interceptor shows every request and response, http and websocket, whole: status, size, time, headers and bodies. Armed, it holds a request before it leaves, lets you edit it, forward it or drop it, on one key. The Autopilot flies the application branch by branch while you watch, never signing out, at a speed you choose. The Cosmos is the live map: every page, flow and request drawn as it happens, and one key dives from the page you are on to the whole application and back.

Sessions are open. Each one is a SQLite database other tools can read, a live HAR that replays signed in, and video of the site and of the console. Lenses read the map in different ways: clusters, hubs, routes, anomalies. A second agent, in red, reads the cosmos beside you and names what it finds.

Artemis is alpha software, and the README says what is real and what is still emulated so the interface could be designed first: the owned browser, the recording, the HAR, the videos, the autopilot and the live map are real; the Interceptor’s proxy does not yet listen on a port, and some Browser-view commands answer as placeholders. It is built with Bun, React, Arwes and cosmos.gl, tested in real Chromium and Electron (267 tests), and runs on macOS, partially on Linux.