app/src/pc.rs runs every pc_action from the worker (admin.spec.md, "PC
control"): one agent-desktop 1.2.0 run per command with a 15 s limit and
its state in the data folder, never --force or raw input, typed text
only through stdin. Each action is decided by permissions::decide for
its asker (not registered, never, ask without consent), then refused
during the emergency stop, while an anti-cheat game runs (Vanguard,
EAC, BattlEye, FACEIT, GameGuard, XIGNCODE3 and the person's list), on
an administrator window and in a password field. Results carry the
window and its elements read again (200 at most, cut to 120 chars),
agent-desktop's error codes become Korean reasons, and each action is
recorded as pc.<action> with the program's file name only.
The emergency stop is a global hotkey (pcControl.stopHotkey, default
Ctrl+Shift+F12) on its own message loop; it kills the running command
and blocks everything but reading until pressed again or lifted on the
PC control screen. features.pcControl (on by default, nothing happens
until someone is registered) and the pinned exe hash decide whether
the brain gets the tool. The installer ships agent-desktop.exe from the
pinned release archive, both hashes checked.
Tested with a fake agent-desktop (342 lib tests pass) and cargo check
for x86_64-pc-windows-gnu; not yet run against real agent-desktop.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The side menu has 대화 right under 대시보드.
- 대화 screen: a "현재 세션" chip (off by default) shows only what came
since the bot was last started. The controller keeps when the latest
start began; history_query takes `session` and answers it back, so the
count line names that start and a new start starts the list over.
- Installer: the shortcuts' icon is a file named by its content
(jarvis-<sha256 prefix>.ico). Windows keeps an icon it has shown by its
path, so after an update the desktop shortcuts kept the old icon. Every
.lnk to jarvis.exe on the desktops and in the start menus (an earlier
version's and the person's own too) now points at the new file, set by
the 64-bit PowerShell: a 32-bit one reads Program Files links as
Program Files (x86). Checked on the Windows VM: 0.1.6 to 0.1.9 left both
desktop shortcuts old; to this build they and search show the new icon.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The start may have read the settings before the save, and the controller
dropped a speed saved with nothing running yet. It now keeps the latest
speed and hands it to the services when they come up. Version 0.1.5.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MeloTTS's own speed shortens every sound and slurred fast speech (Whisper
large-v3 on five Korean sentences, three renders each: 5.5% character
errors at 1.5 and 20% at 2.0, against 1.4% at 1.0). The MeloTTS child now
speaks at most at its natural pace and makes faster speech with a WSOLA
time stretch that keeps the pitch (1.9% at 1.5, 2.2% at 2.0, about 15 ms
per 4 s of speech).
A voice.tts.speed saved while the services run goes to the worker at once
(new tts_speed message) and applies from the next sentence; the client
sends it again whenever the worker connects again. Version 0.1.4.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- while the services run, game mode decides the stage (perf.rs): a game means the game stage at
once (or pause with game.pauseInGame); its end brings the normal stage back after
game.revertSeconds (default 30)
- a change tells the voice worker the LLM switches (llm switching, with a notice), waits until
the brain has written the answers in progress (llm_idle, at most 2 minutes), restarts the LLM in
the stage and tells the worker it is ready or paused
- the game stage runs at 16K context, one request at a time, half the engine's CPU threads and
the game placement (reserve game.reserveGb, default 8, else 2 GiB, else 0 GiB, else pause),
measured once at that context; every placement of a run counts other programs' memory as it
was when the services started
- the voice worker gates every LLM use: on switching new work waits (at most 180 s), the first
spoken request that waits hears the notice once under its own id, on ready all go on, on
paused nothing is answered
- dashboard: "성능 단계: 게임 중 · 게임에 X GB" / 일시정지; game mode screen: game VRAM, revert
wait, pause in game
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- while the services run the app looks at the foreground window every 2 s (Windows): the
person's notGames and games lists first, never a browser, video player, the desktop, Discord,
a launcher's own window or this app; a program under a Steam, Epic, Riot or Battle.net game
folder, exclusive full screen, or a window covering a monitor without title bar or border whose
process uses at least 10% of the GPU's 3D engine (the M0 rule) is a game
- game mode stays until that game's process ends, also behind other windows; the dashboard shows
"게임 모드: 켜짐 (name, reason)" and the game log tab its changes
- a 게임 모드 settings screen (detection on/off, the two lists)
- checked on the win-ci VM: a program in a Steam game folder turned it on after 1.4 s and off
2.0 s after it ended
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- install step browser: Chrome for Testing 157 (pinned SHA-256) into runtime/chrome
- services start it headless with its own profile when features.browser is on; CDP on a free
loopback port passed to the worker as JARVIS_BROWSER_CDP; a failure leaves the services running
- every Chrome connection goes through the app's loopback egress proxy: one lookup, public
addresses only (403 otherwise, no host logged), QUIC off, WebRTC only through the proxy
- stop: Browser.close, then kill after 5 s; dashboard shows the browser's state
- the worker's runtime environment follows the settings step, not every step being installed
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review follow-ups to M5.
- Chat channel names and topics (app/src/channel_sync.rs): a channel with
syncDiscord (default on) gets its name and description as its Discord
name and topic when saved; registering fills them from Discord;
Discord's form of the name is written back; a topic over 1,024
characters is refused before saving; a rate-limited edit is pending and
retried once by itself with the latest text; a missing permission fails
with the reason and the app keeps the text. Commands
discord_channel_info and channel_sync_status. Checked on real Discord
with a temporary channel (fill, edit, rate limit, automatic retry).
- voice.tts.speed (0.5-2.0) on the model screen, passed to the worker as
--melo-speed. MeloTTS's Korean model has one voice, so no voice choice.
- Closing the window runs AdminApi::shutdown first: an install in
progress is cancelled and waited for, the services stop, a failed run's
leftovers (Strata) are cleared (Controller::shutdown). If that fails the
window stays open with the reason; closing again quits.
- WebView2 data goes in the data folder (cache/webview), or a temp scratch
folder before one is chosen, removed at the next start: %APPDATA%\JarvisBot
holds only the location file.
- Command output that is not UTF-8 (CP949 on a PC without the UTF-8
option) is decoded in the OEM code page instead of ending the reading.
Verified on the win-ci VM: closing during the install leaves no process,
no --location keeps only location.json under %APPDATA%, the unit tests on
Windows 168/168.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A stop right after a background start set the LLM's cancel flag, but the
start task then cleared it in Llm::start and went on to download and load
the model. The cancel is now armed in the controller's begin_start, under
its lock (Host::prepare_start -> Llm::arm), and Llm::start never clears
it; a start that finds it set returns before running anything.
wait_gone counted a timeout, a 503 (a server still loading) or an
unreadable answer as stopped, so a failed `launch --stop` could still mark
a live engine off. Only a refused connection confirms the stop now; the
rest keeps checking until the deadline and then reports failed.
Tests: a stop right after a background start runs no launch (and the next
start is not cancelled); a failed stop with a silent or 503 server leaves
the LLM and the services failed through the controller. Fixed-port tests
use an unused port.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
service_start now moves the controller to starting before it returns
(Controller::start_in_background), so a stop right after it cancels the
start and a second start is refused instead of the start running late.
service_restart stops, then starts the same way.
Stopping Strata now confirms the server is gone: `launch --stop` is ended
after 2 minutes with everything it started, then the port must stop
listing a model. A server still answering makes the LLM failed with the
reason, and Services::stop / Running::stop return it, so the controller
shows failed instead of stopped (also for a cancelled start that could
not clear the server). A stop command that fails while nothing answers
counts as stopped.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
M5 step 4, second part. The services start the LLM first: the installed
Strata with the M0 kit's model and normal placement (models in
models/llm, parallel 1, or 2 when a chat channel answers every message,
pictures off, --restart), wait until /v1/models lists the model, and stop
it last. The first start downloads the model; the dashboard shows
Strata's last line and percentage, and stop also cancels a start (the
server is cleared). llm.url uses a server the app does not start.
On every start the app writes config/brain.json (Strata's /v1, the
listed model id, memory/jarvis.db) and hands it to the worker as
JARVIS_CONFIG_PATH. Loading a config with its own db_path no longer
creates ~/.local/share/jarvis.
service_start/service_restart run in the background. Settings gain
llm.context and llm.port (model screen) and llm.url (file only).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each Joined carries a new session number; the core records, when an
utterance's speech_start arrives, the session Jarvis is in, and its Partial
and Final carry that number (Heard.session) even when they arrive after a
leave or a move. The dashboard shows only the current session's captions.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Each start gets a new dashboard; stop ends the event feeding and waits for
it before forgetting, so queued or earlier-run events never reach the
screen.
- AnswerAsked carries the request's speech end and final times, so a second
waiting question does not change the first answer's timing.
- Captions are shown only while Jarvis is in a voice channel.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- control: one Controller starts, stops and restarts the services (stopped,
starting, running, stopping, failed); a failed start leaves nothing
running and keeps its error with secrets masked. The app binary uses it.
- dashboard: built from the core's events alone: the bot's tag, the voice
channel, live captions (screen only, cleared on leaving or stopping), the
last 20 voice answers split into stages with medians (matched by the new
AnswerAsked event), and missed requests without text.
- system: memory in use and per NVIDIA GPU its use and VRAM (nvidia-smi).
- DiscordCore::voice_members, WorkerClient::hello, the conversation's missed
requests shared with the dashboard.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>