@omg-dev/app 0.6.17 → 0.6.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,9 +1,69 @@
1
1
  import { jsx as e } from "react/jsx-runtime";
2
- import { z as n } from "./embedded-CCcPhTYL.js";
2
+ import { z as n } from "./embedded-BcFHPcTF.js";
3
3
  const t = `# Changelog
4
4
 
5
5
  Recent product updates and deployment notes.
6
6
 
7
+ ## August 31, 2026 - An honest token usage inspector and a self-healing session page (v0.6.19)
8
+
9
+ - **Token usage no longer counts free space as used.** The inspector asked
10
+ Claude for a context breakdown and charted the answer as-is. That answer is a
11
+ layout of the whole context window, not a list of what fills it, so it also
12
+ carries a "Free space" remainder, a reserved autocompact buffer, and tool
13
+ schemas that are advertised but never loaded. All of it was drawn as
14
+ consumption. A session that reported 317k of 1.0M listed categories adding up
15
+ to 1.27M, with "Free space" as the largest single entry, and the bar divides
16
+ by that total, so every proportion was wrong as well. The real Messages row,
17
+ which was almost all of the context, showed as a quarter of the bar. The
18
+ breakdown now counts only what occupies the window. Every one of the 585
19
+ recorded snapshots on the development machine was affected.
20
+ - **The mobile transcript appears settled, not mid-move.** A session opened on
21
+ the native app revealed its messages one frame after they arrived, but the
22
+ list keeps correcting its position for up to three seconds, because rows
23
+ mount in batches and an image has no height until it loads. On a real device
24
+ that showed as a transcript parked mid-conversation, with one bubble drawn
25
+ over the tail of the reply above it and the "New activity" pill still up. The
26
+ app now waits for the list to go quiet before it reveals it. A session opened
27
+ while a reply is streaming never goes quiet, so it reveals after 1.2 seconds
28
+ instead of waiting. The opening spinner already covered this moment, so the
29
+ cost is a slightly longer spinner.
30
+ - **The session page recovers from a failed code-split chunk.** Safari could
31
+ show "Importing a module script failed." on a session, from the router error
32
+ boundary, and the page stayed broken. Three parts of the session page loaded
33
+ their code without the retry that the rest of the app uses: the chat engine,
34
+ the assistant message renderer and the diff viewer. A chunk that fails to
35
+ arrive now reloads once and recovers. The background warm-up of the chat
36
+ engine no longer reports its own failure as an error, because the page
37
+ re-requests that code when it renders.
38
+
39
+ ## August 30, 2026 - A flat desktop workspace, agent account names, and remote access in Settings (v0.6.18)
40
+
41
+ - **The desktop workspace no longer draws cards around itself.** The session
42
+ rail and the session stage each rendered as a rounded card with a border, a
43
+ fill and a drop shadow, floating on the app background with a gap between
44
+ them. On a full width window that is chrome around chrome. Both are flat now.
45
+ A single divider line separates the rail from the stage, and the stage runs
46
+ to the window edge. The session header on the stage is 44px instead of 60px,
47
+ because it carries one line of title there. Phones and iPad portrait are not
48
+ affected. They use a different layout that keeps its cards, and the card is
49
+ what makes a stacked list of sessions readable.
50
+ - **Coding agents say which account they are signed in as.** Detection could
51
+ only answer whether an account was connected. A machine with several agents
52
+ under different logins looked the same as one machine with a single login,
53
+ and multi-account Claude showed "Claude 1" and "Claude 2", which name
54
+ nothing. Each agent now reads the credential file its own CLI already
55
+ writes and shows the account. No credential material is copied. A profile
56
+ appears only when you connected an account, so a platform API key never
57
+ reports a login you did not make.
58
+ - **Settings shows how to reach this server from another device.** A new
59
+ Remote access section gives the local URL, and the Tailscale state of the
60
+ machine with the exact command to serve it over your tailnet.
61
+ - **The desktop app keeps scheduled work running after you quit.** The app
62
+ used to attach to any healthy server on loopback and stop its own child on
63
+ exit, which ended schedules with the window. It now owns an isolated
64
+ embedded runtime that stays active after the window closes. A later launch
65
+ reconnects to it. A package update replaces it with the new build.
66
+
7
67
  ## August 28, 2026 - A desktop app preview, unread marks for chats, and the DeepSeek Harness (v0.6.17)
8
68
 
9
69
  - **A chat that landed a reply you have not read now carries a dot.** The
@@ -22,11 +82,11 @@ Recent product updates and deployment notes.
22
82
  two kinds of row now match.
23
83
  - **There is a desktop app preview for macOS and Linux.** It is a Bun-native
24
84
  Electrobun shell that contains the omg.dev web UI and server, so the packaged
25
- app needs no separate Bun or CLI install. At startup it uses a healthy
26
- omg.dev server on loopback when one is already running. Otherwise it starts
27
- its own runtime, and it stops only the child it started. The window is shown
28
- after the app is ready. Builds come from the \`desktop-package\` workflow as
29
- downloadable artifacts. They are not part of this release bundle.
85
+ app needs no separate Bun or CLI install. It always starts and owns an
86
+ isolated runtime, even when another omg.dev server is already running. The
87
+ window is shown after its runtime and app are ready. Builds come from the
88
+ \`desktop-package\` workflow as downloadable artifacts. They are not part of
89
+ this release bundle.
30
90
  - **DeepSeek Harness is available as a coding agent.** It is in the agent
31
91
  catalog, the setup script, and the coding agent adapters, like the other
32
92
  harnesses.