[ Changelog ]
Byte 2.2. Preserve progress, reduce rework.
Keep the task, its requirements and the evidence behind each result together. A compact list and detail workspace connects agent attempts, useful changes, reviewed decisions and unfinished investigations.
[ 2.2.5 · Desktop exit ]
Bound desktop exit outside Chromium's main loop.
Byte now arms a parent-bound plain-Node exit deadline before waiting for the embedded server to finish. The helper exits immediately when shutdown is normal. If Chromium stops pumping the main loop after the server and database owner are gone, it ends the stalled shell after the full 18-second cleanup allowance.
The Windows installer waits beyond that bound before escalating, so an upgrade never replaces files during legitimate SQLite cleanup.
[ 2.2.4 · Desktop exit ]
Close the desktop shell after its data owner exits.
Byte first drains the embedded server, closes the database owner and asks Electron to exit normally. If retained Chromium processes remain alive two seconds later, Byte ends the desktop shell so tray quits and installer upgrades finish.
The fallback starts only after the server shutdown path completes. Existing workspace data, enrolment and preferences remain in place during an upgrade.
[ 2.2.3 · Desktop lifecycle ]
Finish a quit even when the child exit signal never arrives.
Byte still gives the embedded server its full graceful drain window. A host-level deadline now releases the desktop shell if Windows does not deliver the final utility process exit notification after the server and database owner are gone.
This keeps installer upgrades and tray quits bounded on large retained profiles without weakening the normal SQLite shutdown path.
[ 2.2.2 · Startup repair ]
Restore task storage before the first task query.
A new additive migration repairs the exact retained workspace state where an earlier preview recorded integration storage before adding the task execution configuration column. Existing task values remain unchanged and the new field starts empty.
Complete workspaces baseline the repair without changing data. Existing projects, sessions, preferences, enrolment and evidence remain in place.
[ 2.2.0 · Progress ]
Keep a result you can inspect.
Requirements and proof. Version observable outcomes and run their saved checks against an exact revision and environment. Changed code invalidates relevant evidence. Reviewed context, agent claims and screenshots do not independently establish correctness.
Review and continuity. Keep reviewed changes, investigations, rejected approaches and the next experiment beside the task. A verified lesson reproduces a failure and passes on its correction. Review changed requirements before delivering them to a supported agent.
Useful recovery. Prepare selected Git text changes in an isolated workspace, with dependency review and destination checks. Max adds combined-task rehearsal and explicitly configured automatic recovery, bounded by attempts and time. Candidate application requires separate approval by default.
A focused workspace. All agents joins the four integration switches. Work opens as a list with resizable detail. Machine and agent filters keep the selected task, drafts and execution owner intact. Global appearance, keyboard controls and truthful chart tables use one component system.
Compatibility. Existing data, prices and paid capabilities remain. Operator adds manual verification, review and lessons; Scout can inspect and export evidence. Hosted Byte retains its existing local execution boundary. Unsupported native controls keep the affected automation unavailable.
[ 2.1.3 · Repair notes ]
Know what is connected.
Accurate collection. Live indicators use recorded native events, separately from imported history. Child-agent inspection includes captured Codex and OpenCode relationships. Large events retain lifecycle information, and reconnects preserve session identity without duplicating usage.
Useful model pricing. Search a dated offline catalogue across 213 providers. Pricing follows the selected integration. Unknown rates remain unknown, and existing pricing rules stay in place.
Clearer everyday controls. Theme switching and compact density work across the workspace. Model, Project and Session cost drivers use their own grouping. Machine setup is easier to find, and Cody has a compact cat mark beside its detailed companion.
Connection availability. Byte-managed Codex live activity is verified. External Codex hook delivery remains under investigation even after native trust review. Claude execution depends on account permissions. Superset requires its supported, authenticated host. A configured collector or imported history does not mean live activity has been received.
Existing records, preferences, commercial plans and enrolment are preserved.
[ 2.1.2 · Repair notes ]
Connected views. Clearer controls.
Reliable collection. Codex is detected from its Windows application installation. Large histories sync in pages, preserve progress and recover independently when a conversation is unavailable. Connection progress and recoverable errors remain visible.
Correct workspace data. Orchestration, run details and model pricing follow the selected integration and devices. Pattern percentages count distinct sessions, and timeline labels use consistent rounding.
Appearance and Cody. Theme changes apply immediately. Settings now saves interface sizing from 75% to 150%. Cody has a detailed cat companion in its optional panel.
Existing data and appearance choices are retained. Live Codex hooks still require review
in Codex using /hooks. Hosted collection comes from enrolled devices.
[ 2.1.1 · Repair notes ]
What this update repairs.
Integration scope and run ownership. Lists and drill-throughs respect the selected agent, host and data source. Task, run and session links must belong together; switching tools does not transfer active work. Managed runs and Connect check the interfaces reported by the installed CLI.
Task startup and migration 34. The upgrade repairs missing
tasks.source storage that caused recurring background task errors. Existing
source assignments stay intact. Imported tasks recover a source only when their linked
sessions agree; uncertain ownership does not gain local execution authority. Task
records and execution grants are retained.
Native cost reporting. Measured charges stay separate from token-based estimates. Missing data stays unavailable instead of becoming zero. Undated totals remain separate from dated charts and period budgets.
A compact interface. Tighter navigation and controls, the correct Claude Code, Codex, OpenCode and Superset logos, and clearer copy make the selected integration and next action easier to recognize.
[ 35 · Previous release snapshot ]
Byte 2.1.0 and companion surfaces.
Byte 2.1 introduced one workspace for your agents, with clearer navigation, softer controls, useful daily context and charts you can inspect. The earlier surface versions are retained here for reference.
| Surface | Version | What it is |
|---|---|---|
| Server and hooks | 2.1.0 | Express and SQLite, the hook endpoint, the importer and the API. |
| Desktop app | 2.1.0 | Electron, macOS, Windows and Linux, hosting the server in a child process. |
| Client | 2.1.0 | The local and hosted screens, the session mark and the time spine. |
| VS Code extension | 1.2.4 | Live health, tokens and cost in the sidebar. |
| MCP server | 1.0.0 | Thirty typed tools over stdio, HTTP with SSE, or a REPL. |
| This site | 4.0.0 | Six pages, one bundled dependency, nothing fetched from another host. |
Fig. 35 · Six surfaces, six versions.
- Measured
- the earlier 2.1.0 surface versions, retained for reference.
[ 36 · The 2.1 workspace ]
Read down the surface you use.
Claude Code, Codex, OpenCode and Superset share one Byte workspace. Switch the view while connected collectors keep recording. Home, Work, Sessions, Insights and Library bring attention, useful context and measured outcomes into a clearer daily workflow. Your theme, density, accents, records and enrolment carry forward.
Save private decisions and handoffs, preview sharing with an explicit audience, and launch versioned recipes with their existing checks. Project and organisation budgets show collection coverage. Factual briefs use recorded activity without background model calls. Updated controls and charts support keyboard inspection, exact tables and exports.
Six lanes, one per surface, in the order of the table above. The numbers are in that table; what the lanes add is the distance between them. The server and the desktop app and client set the same three bars in this 2.1.0 snapshot. The VS Code extension keeps its own version. The MCP server draws the shortest lane on the plate, still at its first release. This site is the one drawn the other way round: a full first bar and nothing after it, where every other surface has a short first bar and the length further along. Each lane also carries what ships in that surface, as counts, and one line for the thing a count cannot say.
Fig. 36 · Six surfaces, and what is in each.
- Measured
- the versions and the counts in the repository at the time of writing.
[ Check your own ]
Settings tells you what you are running.
Version, UI build, uptime, Node version, platform and connected clients, in the About panel. Or ask the CLI.
byte doctor # check the install, and what version answered[ Get it ]
Updates are part of the licence.
Every tier gets every version. There is no upgrade fee and no maintenance plan.