- Settings `features` (weather, webSearch, meals) and `mcpServers` (name, command, args, env names,
enabled), edited on the new 기능 screen. The tools of a feature that is off go into the brain's
`disabled_tools`; only enabled MCP servers go into its `mcps`.
- MCP environment values (API keys) live only in the encrypted secrets (`mcp:<server>:<NAME>`),
shown as stored or not, masked in logs, removed with their server, and reach the worker only in
`JARVIS_MCP_ENV`, which the brain takes out of its environment before giving each server its own.
- `enabled_builtin_tools(cfg)` is the one list the router, toolSearchTool and the executor use, so
a turned-off tool is neither offered nor run, also when the model names it.
- The v2 brain never offers v1's `localFiles` (home folder read/write/delete) and `screenshot`:
anyone in the voice or chat channels could ask for them. Screen viewing comes in M7.
- The brain connects MCP servers on its own thread and logs each outcome without debug logging.
- Stored secrets are masked in the log hub as soon as the data folder is found.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A rate-limited edit of a newly registered channel is retried with the
same "never clear Discord with an empty field" rule (it was retried as
an existing channel and cleared the topic).
- Channel edits go one at a time, and Discord's form of the name is
written back only while the settings still hold the name that was sent,
so a slow answer to an earlier save never overwrites a later one.
- The chat channel screen drops a Discord name/topic lookup that answers
after the ID was changed.
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>
Found running the app's admin commands on the game PC (Windows, RTX 5070
Ti): the full install, Strata started by the app downloading the 22.9 GB
model, the worker and Discord up, five spoken questions all answered.
- Windows refuses a connection to a closed local port only after about
2 s, so the 2 s request timeout made every stop "not confirmed". The
check now waits up to 10 s to connect and still counts only a refusal
(not a timeout) as stopped.
- Strata 0.1.59 reports the model download as "X of Y GB"; percent()
reads that, and the dashboard shows the current line's progress only
(it had stayed on the engine download's 80 %).
- Strata and the NVIDIA shader cache write under %APPDATA% whatever
STRATA_* says: the layout sets APPDATA inside the data folder on
Windows, next to LOCALAPPDATA.
Roadmap: M5 step 5 done.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
M5 step 5, first part. app/shell is a Tauri 2 crate (jarvis.exe): one
window over app/ui whose invoke("admin") goes to AdminApi::call. Its
WebView2 data sits next to the location file; closing the window stops
the services and waits for a cancelled start (AdminApi::shutdown).
app/shell/package.sh cross-builds it on Linux (x86_64-pc-windows-gnu)
and lays out Jarvis/ with WebView2Loader.dll and python-src/
(voice_worker, jarvis). The worker's default sources are python-src next
to the executable when present, else the repository's src/.
The bot screen now shows the masked token right after saving.
Checked on the win-ci VM: the window and wizard, PC check, uv and worker
venv installed, a cancel leaving no uv/Python process, the token stored
DPAPI-encrypted, a start failing with its reason, logs, error copy, zip
export, closing the window ending the process, nothing under %APPDATA% or
%LOCALAPPDATA%; the core's unit tests on Windows (156/157, the one
Linux-path assumption fixed).
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>
- A cancelled command ends with every process it started (process group on
Unix, taskkill /T on Windows).
- Waiting for a response or the next chunk gives way to a cancel, so a
silent server cannot hold the install.
- Pointing the settings at the runtime is the last install step: a failure
shows as failed and can be retried; done means written.
- Strata's installer gets its folder as the working folder, not inside the
script text.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- download: resumed downloads checked against a pinned SHA-256.
- install: uv 0.11.20, the worker/brain venv (Python 3.12, the new
src/voice_worker/requirements-brain.txt), the MeloTTS venv (Python 3.11,
PyTorch cu128), Whisper large-v3-turbo, the Korean MeloTTS voice and
Strata, the M0 kit's recipe; markers per step and version, cancel, retry,
everything (caches, temp, HF and NLTK data) inside the data folder, the uv
cache cleaned and the worker settings pointed at the venvs when done.
- The services give the worker the same environment once installed.
- The wizard's model step shows and drives the install.
Installed from an empty folder on Linux and started the services on it:
worker connected, STT and TTS ready, nothing written outside the folder.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- app_status reports firstRun until wizard_finish; wizard_step saves the
step reached in config/setup.json, and the wizard resumes there (a stored
token lets the bot step go on).
- show() and refresh() drop answers that arrive after the screen changed.
- folder_choose points the log hub at the folder's logs/ at once.
- Choosing another server clears the voice channel picker.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- admin_api: the one entry point of the screens (app status, data folder,
PC check, Discord token check and pickers, settings, service control and
the dashboard, logs query, error report and zip export).
- discord_setup: token, Message Content and invite link checks over REST.
- app/ui: first-run wizard, dashboard, five settings screens and the log
screen in plain HTML/CSS/JS (dark theme after DESIGN.md, Korean text).
- jarvis-admin-dev: a loopback, token-guarded development server so the
screens run in a browser against the real commands.
Checked in a browser with the real test bot and voice worker: wizard
steps, start/restart/stop, settings save, chat channels, logs and export.
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>
- redact: a token with sentence dots around it is masked too.
- Worker error messages are always logged (code and id), so the log screen
and the error report show them without debug logging.
- The voice worker logs with stt, llm and tts categories, so its lines land
in those tabs.
- The zip leaves out the oldest lines by the time they were logged, across
every tab's file, not by file name.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- datadir: the data folder layout, the location file (JARVIS_DATA_DIR wins),
free space for the wizard.
- settings_edit: the fields the five settings screens edit; apply writes only
non-defaults, keeps unknown keys and writes nothing unless the app's own
check passes. A memory section reaches the worker's hello.
- secrets: config/secrets.dat, DPAPI for the Windows user; the services take
the bot token from it before JARVIS_DISCORD_TOKEN.
- logs: the log hub behind the log screen (tabs, daily files kept 14 days,
the recent error report, a zip under 10 MB, secrets and token-shaped text
masked); the log macros and the worker's output feed it.
Spec: app/src/admin.spec.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>