0
Fork 0
mirror of https://github.com/zeronsh/comet.git synced 2026-11-16 18:57:19 +00:00

Compare commits

..

16 commits

Author SHA1 Message Date
Wing
f6a9bbfc29
Merge pull request #1468 from zeronsh/zeron/main-catches-up-0.3.7
main catches up with the release line (Zeron 0.3.7)
2026-11-15 16:41:56 -07:00
Wing
55a5c39219 Zeron 0.3.7: Cloud chats switch accounts; a scroll away stays away
0.3.6 plus:
- A Cloud chat's model menu offers Cloud's accounts again, to switch the
  provider account every Cloud machine uses (#1467).
- The transcript no longer pulls you back to the end after you scroll away:
  not during a send's glide, nor at a resize after a scroll (#1450).

Version 0.3.7.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 16:41:46 -07:00
Wing
3344446195
Merge pull request #1450 from zeronsh/zeron/transcript-scroll-away
Transcript: a scroll away from the end stays where it was taken
2026-11-15 16:41:32 -07:00
Wing
2fc1d11aeb
Merge pull request #1467 from zeronsh/zeron/cloud-model-accounts
Composer: a Cloud chat's model menu offers Cloud's accounts
2026-11-15 15:54:30 -07:00
Wing
19b04d04d5 Composer: a Cloud chat's model menu offers Cloud's accounts
A chat on a Cloud machine had no Account row in its model menu: its
accounts were asked of the machine (`cloud-…`), which the engine doesn't
answer for, and whose accounts aren't its own anyway. Cloud's are the
vault's, every Cloud machine's alike, which this engine answers for under
"cloud" (crates/engine cloud_accounts), as Settings → Providers shows them
under Cloud (#1456). Any Cloud device (a chat's machine, the account's
Cloud device) now reads, switches and refreshes those; a machine is never
asked (it would be woken).

Test: model_accounts' "a chat on a Cloud machine reads and switches
Cloud's accounts" (fails without this: the machine was asked). Full UI
suite (1425) passes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 15:54:23 -07:00
Wing
68e460af25
Merge pull request #1457 from zeronsh/zeron/main-catches-up-0.3.6
main catches up with the release line (Zeron 0.3.6)
2026-11-14 21:14:06 -07:00
Wing
e48dcbed12 Zeron 0.3.6: Cloud's providers managed again; Cloud machines come online
0.3.5 plus:
- Settings → Providers: Cloud is a choice again while it's on, its
  accounts (Claude Code, Codex) and API keys managed there (#1456).
- Cloud: the updater and the pre-sleep tidy keep zeron-engine, which
  `zeron headless` runs (#1455; the edge's install and repair, #1454, are
  live).
- Plugins: read the composer's draft and set it aside; compose can replace
  it or write another chat's (#1445, #1452, #1453).
- Browser: a load error over a page that drew can be dismissed (#1431).
- The "Task completed" chime and banner come on a finished turn, not your
  own send; a banner's click opens its chat.

Version 0.3.6.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 21:13:50 -07:00
Wing
7e1f34316a
Merge pull request #1456 from zeronsh/zeron/providers-cloud
Providers: Cloud is a choice again, its accounts and API keys managed there
2026-11-14 21:13:34 -07:00
Wing
739ab4187f Providers: Cloud is a choice again, its accounts and API keys managed there
Zeron 0.3's Settings → Providers listed only computers, so Cloud's
providers (the vault's logins and keys every Cloud machine uses) couldn't
be managed at all. As 0.2 did, Cloud is one more choice after the
computers while Cloud is on (`agents.target("cloud")`, which the engine
answers from the vault: crates/engine cloud_accounts).

- Its cards: Claude Code and Codex, their accounts (sign in, switch,
  remove), with no switch, settings or Update (`ProviderCard.fixed`), and
  nothing to install or add.
- Its API keys: Anthropic's and OpenAI's, saved to the vault for the
  account's Cloud device (`agents.cloud_key` → VaultPutApiKey), the key
  every Cloud machine uses from its next turn.
- devices.picker takes extra choices; the page's body is Cloud's own.

Tests: ui/tests/providers_cloud.test.luau (Cloud offered while on, its
cards and keys, back to this computer; none without Cloud); agents'
`a_cloud_key_is_one_cloud_runs_for_its_device`. Full UI suite (1424) and
agents:: (12) pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 21:13:25 -07:00
Wing
59783f1516
Merge pull request #1455 from zeronsh/zeron/cloud-updater-keeps-engine
Cloud: the updater and the pre-sleep tidy keep zeron-engine
2026-11-14 20:35:46 -07:00
Wing
9f43edfee7 Cloud: the updater and the pre-sleep tidy keep zeron-engine
Since 0.3.0 the release's `zeron` is the zgx app, whose `zeron headless`
runs the `zeron-engine` beside it. The updater (staging a release) and the
tidy (pre-sleep, on installed versions) left it out on Cloud
(`CLOUD_UNUSED_FILES`, 451822be9), so a machine that updated stopped coming
online. Nothing is unused on Cloud now. (#1454's repair, before each start,
covers the releases out there until this one is.)

Tests: the updater's (74) and transaction tests (30), with the Cloud ones
now asserting it's kept.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 20:35:40 -07:00
Wing
a30749df6d
Merge pull request #1454 from zeronsh/zeron/cloud-keep-engine
Cloud: keep zeron-engine, and put it back before each start
2026-11-14 20:29:17 -07:00
Wing
7e1d53000a Cloud: keep zeron-engine, and put it back before each start
New Cloud machines never came online: since 0.3.0 the release's `zeron` is
the zgx app, whose `zeron headless` runs the `zeron-engine` beside it, and
the installer deleted that file (451822be9, when headless linked the
engine). The unit exited at once ("no engine beside …/zeron (zeron-engine)"),
restarted every second, never enrolled, and the chat said "Starting a Cloud
machine…" until the 10-minute limit. 0.3.5's own updater and pre-sleep tidy
leave it out on Cloud too, so a machine updating on a wake broke the same way.

- The installer keeps zeron-engine, and downloads again a version that's
  installed without it.
- A repair (`~/.zeron/repair-engine`) runs before every start of the unit
  (`ExecStartPre=-`, never failing it): with `current` missing zeron-engine,
  it fetches that version's release from the edge and puts the file back.
  The installer sets it up, and so does every wake's first command, so
  machines set up before this get it as they wake (reloading systemd once).

Tested: the install script's unit tier (keeps it, re-downloads a version
without it, the repair restores it and is a no-op once there, a failed
download never fails a start, the wake writes the repair once); the real
0.3.5 release on Linux (restored byte for byte; `zeron headless` then
starts and enrolls); edge unit (100) and Cloud workerd (77) tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 20:29:07 -07:00
Wing
93bed8f397
Merge pull request #1453 from zeronsh/zeron/plugin-draft-replace
Plugins: compose can replace a draft's words or write another chat's; draft_of reads any chat's
2026-11-14 19:58:22 -07:00
Wing
c10b5ac3f4 Banners: no "finished" on your own send, and a click opens the chat
A finished banner (with its sound) rang as you sent. The engine's notifier
rings when a session's completion marker moves, and your own message
often moves it: a steer or a queued row taken as a turn ends publishes
that end with Working (your message carries the turn on), and a send that
replaces the runtime marks the old turn's end (a held wait's included) a
moment before your turn starts. The old app's chime kept quiet for a send
in flight; the engine, which now rings for the zgx app, never knew. Now a
finish published with the next turn running never rings, and the rest
wait two seconds to stand: a turn starting meanwhile takes the finish
with it. Questions and failures still ring at once.

Clicking a banner did nothing. The engine posts Zeron's banners, but
macOS hands a click to the app its bundle names (Zeron.app's interface),
never to the engine that posted it, so the engine's own route (`open -a
… zeron://notification/…`) never runs. Zeron.app's interface has always
taken the click itself (`notify::on_click`); the zgx app never did. It
does now: Zeron comes forward and opens the banner's chat (agent updates:
Settings → Providers), through the same route a link takes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 19:45:09 -07:00
Wing
56e6886625 Transcript: a scroll away from the end stays where it was taken
Two ways the view was pulled back to the end after a person scrolled
away from it:
- A send's glide (the prompt rising to the view's top, or a steer's
  waiting up to 2 s for its prompt to land) went on to the end over a
  scroll taken meanwhile. A wheel now stops the glide where it is; the old
  reply keeps the room it held until it's out of view, so nothing shown
  moves.
- A scroll begun within 300 ms of the view's size changing left the end
  held, and the next resize, however much later (the sidebar, a panel,
  the window), went back to it. Resting away from the end now lets it go
  when a person scrolled since the last resize.

ui/tests/transcript_scroll_away.test.luau: both fail on main, pass here.
The full UI suite passes (1405).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 17:06:34 -07:00
23 changed files with 906 additions and 108 deletions