arkna-router

The machine boundary behind arkna watch. You probably want that command, not this package.

npm install -g arkna
arkna login
arkna watch install
arkna watch

arkna watch loads this package in-process, so installing it separately gains you nothing.

What it does

Runs a local HTTPS proxy that records AI model calls crossing this machine, including calls from agents that were never told Arkna exists. It installs a certificate, points the system proxy at itself, and writes an environment file that new terminal sessions read.

Recording only. Nothing is blocked.

What it does not reach

Named in full by arkna status, and worth reading before you rely on it. In short: anything already running, providers outside the intercepted list, containers and virtual machines, clients that pin their own certificate, and anything that sets its own proxy after the shell starts.

Arkna does not claim total capture. The measured figure comes from reconciling what crossed this boundary against the provider's own usage record, which is what arkna status reports.

What your agents are called

The boundary sees the executable, not the program. Two agents you wrote both run as python.exe, so both are recorded as python-app. To tell them apart, name them in ~/.arkna/router-config.json:

{ "agentMap": { "python.exe": "Claims Triage Agent" } }

That is one name per executable, which is as far as this vantage goes. Code you own is better served by the SDK, which names itself: arkna.init(api_key="ark_...", agent_name="Claims Triage Agent").

One failure mode to know about

If the system proxy points here and this is not running, the machine has no internet at all, including the browser you would use to find out why. Stopping with Ctrl+C puts the machine back, and arkna watch uninstall removes everything.

Platforms

macOS is complete. Windows sets the registry but does not refresh running applications. Linux prints what to do rather than doing it.

MIT