The web app (PWA)
이 쪽은 아직 한국어로 옮기지 않았습니다. 아래는 영어 원문입니다.
elanous ships a web dashboard — the PWA — next to the terminal UI. The package already contains the built web app, so there is nothing to build.
Open it
elanous nexus run # start the daemon; the web app is served with it
elanous nexus show # print the web app, REST and event-stream links
Open the link that nexus show prints in any browser on the same machine.
The port is picked when the daemon starts (usually 31415, or the next free
one if that is taken), so use the printed link rather than a fixed number.
Stop a daemon you started by hand with elanous nexus stop.
What is in it
Status comes from one maturity table that every surface reads. Stable screens are shown to everyone. Experimental and Tool screens are hidden until you set the screen role to Contributor in Setup (/setup → screen role); Operator screens are for the person who runs the machine (Owner). Experimental screens work, but their layout and behaviour may still change.
| Menu | Status | What it does |
|---|---|---|
| Chat | Stable | Talk to elanous with streaming replies, pick a session, a backend and a surface, and see the running budget. Voice input is available where the browser allows microphone access. See Chat. |
| Terminal | Stable | Live terminals from your machine in the browser — several tabs, a modifier-key bar for touch keyboards, file and camera attachments, a mirror of the terminal UI, and a live view of an agent's terminal from a link. See Terminal. |
| Editor | Stable | Since 0.2.21 in the default menu (Create). Write and edit workflows and harness run graphs on a canvas — add nodes, connect them, and save them. Starting a run from the editor and watching each node's status needs operator access. |
| Intake | Experimental | Since 0.2.3. One box for anything you want elanous to take — a link, a memo, a list or an instruction. It shows as you type how it reads the text, then you absorb it into your notes or send it to the harness. See Tasks and intake. |
| Approvals | Tool | Things waiting for you: loop steps that ask a person before they go on, and pull requests held for your approval — each with its summary, changed files and checks. Approve, and the pull request is merged. |
| Live | Stable | Your harness runs as they happen — stage bars, a stream of decisions (what, why, where to), gauges and the raw log. Everyday mode costs almost nothing; Full show records more and animates it, and switches itself off after 30 minutes. See Live. |
| Trace | Experimental | Follow one run from the whole fleet down to a single decision and the log line behind it. Filters stack up as a lens you can peel back one chip at a time, and the address keeps the view so you can share it. See Trace. |
| Missions | Experimental | Mission lineage and the task board in one menu; you can also hand a new goal from here. In the Missions list, a mission with no update for at least 14 days and a non-terminal status shows an amber “N일 멈춤 · 마지막 갱신 YYYY-MM-DD” label; an autonomous mission in that state also shows 닫기 제안. Done, completed, failed, disarmed, rejected and cancelled missions do not get this inactivity label. |
| Design | Tool | Pick a design system, see drafts, or derive one from a URL. See Design systems. |
| Vault | Experimental | Browse your Obsidian vault, read and edit notes, create new ones, and explore tags and the link graph. See Vault. |
| 마켓 (Market) | Stable | Browse the signed plugin marketplaces, read a plugin's capabilities, install and remove plugins. See Plugins. |
| Schedules | Operator | Every scheduled job in one list — cron, the background service and loop triggers. |
| Settings | Experimental (always shown) | Models and tiers, voice and text-to-speech, persona, notifications, theme and daemon health. |
Setup (/setup) | Stable | First-time setup in the browser. Today it covers the LLM provider; the other wizard steps still run in the terminal with elanous onboarding. |
Use it from another device
Share the web app over your Tailscale network:
elanous nexus pwa share enable
elanous nexus pwa share status
Other devices on the same tailnet can then open the link that
elanous nexus show prints. Every device on your tailnet can reach it, so
only share on a tailnet you trust. Turn it off with
elanous nexus pwa share disable.
Connect each device once
From 0.2.3, a device that opens the web app through the
tailnet link needs a token once. The browser on the daemon's own machine
(localhost) does not.
A device that is not connected yet shows a banner saying it is not connected to the daemon (인증 필요 — authentication needed). To connect it:
- On a device that already works, open Settings › Connect token (other devices) and press Generate connect token, then copy it.
- On the new device, open Settings › Daemon and paste it into Bearer token.
The token is kept in that browser, so you do this once per browser.
If the link stops working from another device, check
elanous nexus pwa share status and run elanous nexus pwa share enable
again.
Troubleshooting
- The page does not load — run
elanous nexus show; if no daemon is listed, start one withelanous nexus run. - Something is missing after an update — first run
elanous nexus restart-needed. It only reports; it restarts nothing. Restart the daemon only when it says a restart is needed. - Run
elanous doctorto check credentials and setup.