Commit Graph

58 Commits

Author SHA1 Message Date
javis-bot
999c432216 chore(app): version 0.1.42
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 01:04:08 +09:00
javis-bot
912b3304ac chore(app): version 0.1.41
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 00:47:51 +09:00
javis-bot
2a57b2b2f4 chore(app): version 0.1.40
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 23:32:37 +09:00
javis-bot
2e00104332 chore(app): version 0.1.39
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 22:43:18 +09:00
javis-bot
39ac20682e feat(app): PC control through agent-desktop, with the emergency stop and the anti-cheat block
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>
2026-11-18 22:42:48 +09:00
javis-bot
a59ed43ae1 chore(app): version 0.1.38
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 20:55:42 +09:00
javis-bot
4d83543acf chore(app): version 0.1.37
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 20:42:30 +09:00
javis-bot
f05424e1b2 chore(app): version 0.1.36
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 20:08:35 +09:00
javis-bot
c816358552 chore(app): version 0.1.35
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 18:32:50 +09:00
javis-bot
49050b18a9 chore(app): version 0.1.34
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 18:09:12 +09:00
javis-bot
e428aad58a chore(app): version 0.1.33
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 17:25:49 +09:00
javis-bot
a665dd8d21 revert(voice): back to upstream songbird 0.6.1, nothing was heard with the held-packet patch
With 0.1.32 (songbird vendored with packets of an unnamed SSRC held until
Discord's Speaking op names it) the bot heard nobody on the live server
from its 16:57 join on 2026-11-18, while 0.1.30 heard every request at
15:58 the same day, and the speaker's Discord was heard by everyone else.
The patch is the only receive change between the two, and the cause was
not found (it passed the two-bot test server runs), so it is removed and
the first ~100 ms of a speaker's first utterance after a join is lost
again, as in 0.1.30.

This reverts 81d1e26 and 9199ccb.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 17:24:58 +09:00
javis-bot
a5afdbb221 chore(app): version 0.1.32
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 16:22:30 +09:00
javis-bot
2a95f58a0e chore(app): version 0.1.31
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 16:15:23 +09:00
javis-bot
81d1e26f61 fix(voice): keep the first packets of a speaker until Discord names them
Discord names a speaker's SSRC in the Speaking op only the first time
they speak, and the op arrives after their first UDP packets. songbird
0.6.1 dropped the DAVE packets it could not decrypt yet, so the first
~100 ms of the first thing each person said after a join were lost
(live 2026-11-18: "자비스 서울 날씨 어때" arrived as "아비 서울날씨
어때", and the first call after the 01:20 start as "아비스").

songbird is vendored in app/vendor/songbird with one patch: packets of
an unnamed SSRC are held (1 s, 50 packets each, 32 SSRCs) and processed
in arrival order once it is named, and the Speaking event is sent before
the SSRC is named so handlers know the speaker first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 16:15:07 +09:00
javis-bot
2e90c47a95 chore(app): version 0.1.30
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 11:21:46 +09:00
javis-bot
b4f8f71dd2 chore(app): version 0.1.29
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 11:08:15 +09:00
javis-bot
1bef5db912 chore(app): version 0.1.28
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:57:23 +09:00
javis-bot
ecde1e6bd0 chore(app): version 0.1.27
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:05:45 +09:00
javis-bot
68d0333698 chore(app): version 0.1.26
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 09:24:11 +09:00
javis-bot
1c06b16bd4 chore(app): version 0.1.25
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 15:48:01 +09:00
javis-bot
61b68130c6 chore(app): version 0.1.24
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 15:40:48 +09:00
javis-bot
d02092662b chore(app): version 0.1.23
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 13:07:48 +09:00
javis-bot
4993942040 chore(app): version 0.1.22
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 10:11:59 +09:00
javis-bot
07615ee7a1 chore(app): version 0.1.21
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 21:13:39 +09:00
javis-bot
6a9b66bdcd chore(app): version 0.1.20
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 17:26:56 +09:00
javis-bot
65294f3f97 chore(app): version 0.1.19
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 16:12:20 +09:00
javis-bot
9a91bc9ab6 chore(app): version 0.1.18
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 15:56:40 +09:00
javis-bot
fdcaae4820 chore(app): version 0.1.17
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 15:43:10 +09:00
javis-bot
80ce9281a3 chore(app): version 0.1.16
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 15:29:51 +09:00
javis-bot
1cdfbf5151 chore(app): version 0.1.15
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 12:33:38 +09:00
javis-bot
1f2a8ec05e chore(app): version 0.1.14
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 12:20:33 +09:00
javis-bot
04b516dbc1 feat(app): 한 일 as a view of the 로그 screen, shortcuts to a left-behind copy start the current Jarvis
The 한 일 screen is gone: 로그 has 로그 and 한 일 views switched at the top.

An update before 0.1.12 could install into Program Files while the desktop
shortcut kept pointing at the first install's folder, an old copy that no
update reaches: its jarvis.exe shows the old icon and starts a second, old
Jarvis next to the running one. The installer now points every desktop and
start menu shortcut to another Jarvis install's jarvis.exe at this install.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 12:20:33 +09:00
javis-bot
b386c905b2 chore(app): version 0.1.13
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 12:04:00 +09:00
javis-bot
fd7ccab55b fix(app): shortcut icons in start menu folders and any install folder, updates go where Jarvis is
- The icon pass also walks the start menus' folders, so a shortcut kept
  in one (and a later icon change) is not missed.
- The install folder and icon path reach PowerShell through the
  environment: a folder name with an apostrophe broke the whole command.
  A failure is now a line in the install details.
- InstallDirRegKey read the 32-bit registry view before .onInit switched
  to the 64-bit one where the folder is written, so a silent update of
  Jarvis installed elsewhere put a second copy in Program Files. .onInit
  now reads the 64-bit key; a folder given with /D wins.
- Version 0.1.12.

Checked on the Windows VM with Jarvis 0.1.6 in C:\Tools\Kim's Jarvis and
shortcuts on both desktops and in start menu subfolders: 0.1.11 left the
desktop and subfolder shortcuts old; 0.1.12 (no /D) updated that folder
and every shortcut, and a fresh 0.1.12 still goes to Program Files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 10:56:24 +09:00
javis-bot
2b832c1c3b feat(app): 앱 last in the side menu, version 0.1.11
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 10:47:03 +09:00
javis-bot
3d8801b691 chore(app): version 0.1.10
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 10:42:09 +09:00
javis-bot
1a12755649 feat(app): 대화 under 대시보드, a current session view, shortcuts that follow the app icon
- 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>
2026-11-16 10:42:09 +09:00
javis-bot
fbdf274b9d chore(app): version 0.1.9, an installer that starts
The 0.1.7 and 0.1.8 installers were built with NSIS 3.0.4.1 stubs under
makensis 3.10 and crashed at start (0xC0000005) before installing
anything. 0.1.9 is the same app built with makensis's own stubs, checked
on the Windows VM: silent install, the close button set to tray hides
the window and a second start shows it, the tray icon shows it again,
the real X hides it, the tray menu's 완전 종료 quits, and the close
button set to quit exits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 09:56:33 +09:00
javis-bot
2a6b350079 feat(app): app icon, close button to quit or hide to the tray, one Jarvis at a time
- New icon (voice bars in a ring on the accent gradient; three thicker
  bars at 32 px and below) for the program file, window, taskbar,
  installer and a tray icon of its own.
- 앱 settings screen with app.closeButton: "quit" (default, as before)
  or "tray", read each time X is pressed (no restart). Tray mode only
  hides the window; the bot and services keep running. The tray icon is
  always there: a left click shows the window, its menu has 열기 and
  완전 종료 (the same stop-then-exit as closing).
- tauri-plugin-single-instance: starting Jarvis again while it runs
  shows the running one's window instead of a second app driving the
  same services.
- Version 0.1.8.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 09:37:08 +09:00
javis-bot
53d522db69 fix(app): update screen no longer shows "null" when there is no new version
The update screen passed a missing release-notes card straight to the
DOM's replaceChildren, which writes null as the text "null" (h() skips
nulls, replaceChildren does not). Version 0.1.7, which also carries the
대화 screen and the kept answer traces.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 09:24:50 +09:00
javis-bot
46f71e7f03 feat(app): 대화 screen to read what people said, Jarvis's answers and how each answer was made
The management app reads the worker's history store (read only) and shows
people's words, Jarvis's answers and the answer traces in time order, with
filters for kind, place, person, channel, day and text, live follow, older
items on demand and expandable traces (records given, tools offered, plan,
model thinking, tool calls and results).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 03:08:38 +09:00
javis-bot
2a140d8490 fix(installer): count the uninstall size at build time instead of walking the install folder
The setup ran GetSize on the whole install folder for the uninstall entry's size. With the data
folder kept inside it (models, Python runtime) that walked tens of thousands of files after the
install had already finished, which looked like a hung install. The size of what the setup
installs is now counted by installer.sh and passed in.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 02:48:24 +09:00
javis-bot
27eb1315b9 fix(tts): MeloTTS speaks up to 1.25 itself so fast speech sounds natural
Stretching all of the speed-up from 1.0 kept every sound but sounded
awkward (UTMOS 3.13 at 1.5, against 3.73 for MeloTTS's own 1.5), while
MeloTTS's own speed past 1.25 drops sounds (sentence-final "요" and first
syllables, 4.6% character errors at 1.5). MeloTTS now speaks up to 1.25
and the WSOLA stretch does only the rest, with a 5 ms search: 2.6% and
UTMOS 3.56 at 1.5 through the real child. Version 0.1.6.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 00:06:52 +09:00
javis-bot
8a37144cd8 fix(app): a speech speed saved while the services start reaches them once they run
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>
2026-11-15 23:46:30 +09:00
javis-bot
dbe5c617bc feat(tts): change the speech speed without a restart and keep fast speech clear
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>
2026-11-15 23:39:04 +09:00
javis-bot
d17a3bbb61 feat(app): speak the transcription notice on joining a voice channel instead of posting it in chat
The notice (voice.joinNotice) is now a speech request in the voice channel.
It is owed from each join until some of it was played or someone stopped
it; when the worker cannot speak yet (auto-join while it still starts) it is
spoken as soon as the worker is ready. Version 0.1.3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 23:13:31 +09:00
javis-bot
f991981776 fix(app): the worker runs the Python sources shipped with this app, not a folder another install stored
The first-run setup writes voiceWorker.cwd; when it ran from another
install, an updated app kept starting that install's older sources (found
on the game PC: 0.1.1 ran without the screenView tool). Shipped sources
next to the executable now always win. Version 0.1.2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 22:43:06 +09:00
javis-bot
a85ad3e00f chore(app): 0.1.1, with the window's lock file brought up to date for screen viewing
The window's Cargo.lock still lacked jpeg-encoder and windows that screen
viewing added to the app core, so the --locked Windows build stopped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 22:27:14 +09:00
javis-bot
f71c72d3a1 fix(installer): the driver's failure reason reads as Korean, not garbled text
The app writes the reason in UTF-8; FileRead took it for the system's ANSI
code page, so a declined driver install showed mojibake in the message box
and in the details. Read the file's bytes and convert them from UTF-8, for the
install and the uninstall message alike.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 00:30:41 +09:00