lofiwave
Connecting…

Sessions

PIDTypeSessionWorking dirCommandUpCPUMemRun
AppCommandRunningLast run

Running app processes

PIDTypeSessionWorking dirCommandUpCPUMemRun
WorkflowScheduleLast runOn

Let an agent run lofiwave

Give an agent this URL and an API key. It can then create workflows, start sessions and read runs for you.

API keys

NameKeyCreatedLast used

Run targets

Where sessions and workflows can run besides this machine. An E2B target gives each run its own sandbox VM, with a live terminal you can open from Sessions. Needs E2B_API_KEY in lofiwave's environment.

NameWhen idleTemplateUsed by

Run configs

Custom instructions, environment variables (API keys) and, optionally, a Docker image with volumes, to attach to any session or workflow. Values are kept in lofiwave's database and never shown in full.

NameInstructionsEnvDockerUsed by

Appearance

Saved in this browser.

lofiwave

ProcessProcsMemoryCPUUp

Agents started elsewhere

AgentCommandProcsMemoryCPUUp

Memory is resident memory (RSS) summed over each process tree: an agent with its node and MCP servers counts as one. Shared pages count in every process that maps them, so the sums can exceed what the machine reports as used. CPU is in % of one core. Updates every few seconds while this page is open.

Plan limits as of each agent's last request on this machine. Claude's come from the statusline of sessions lofiwave started; Codex's from its rollouts in ~/.codex/sessions, which every Codex session writes. A bar's tick is where an even pace through the window would be by now.

#Workflow / typeTriggerStatusStartedDurationExit
New process type
NameKindCommandArgsDetectFound

New session

More options

New workflow

More options

Each run opens as a live session you can watch and type into. Claude runs close once the agent is done and idle.

New E2B target

More options

New config

Docker

Resume a session

Choose a folder

Sign in

Your name shows on the runs you start and in who's online.