[beamiter]

Why

Frost needs a session-first workspace so users can find and continue CLI agents, API conversations and native tasks without switching desktop apps.

Changes

• Add a persistent searchable session sidebar and central Terminal/API/Task surfaces, replacing the horizontal session strip.
• Connect CLI sessions to the shared persistent PTY host, including reconnect, exclusive input ownership and duplicate-launch prevention.
• Share API chats, full paged history, read positions and revision-checked drafts through the exact submission-receipt bridge.
• Add multiline native/API input, Claude follow-up turns, verified Codex resume/history and task defaults that retain explicit opt-outs.
• Move provider discovery into a bounded background cache and keep the inspector closed by default.
• Pin both core dependency entries and Cargo.lock to merged jterm_core 589a26658f548ec96ff60a53ea65804901ed5c7b; update and verify source-bundle provenance.

Validation

• cargo check --locked --offline --all-targets against the actual published Git core passed with no local path patch.
• Full cargo fmt check passed; strict frontend Clippy passed.
• Shared bridge 9/9, agent sessions 29/29, API chat 19/19, native-task 38/38 and actual PTY 27/27 focused suites passed.
• Actual Xvfb smoke tests covered cross-frontend API history/drafts and managed CLI detach/restart/reconnect with one provider invocation and the same process.
• Source archive bytes and executable modes match the published Git tree; source-bundle offline locked resolution passed.
• Six layout geometry failures already occur on unchanged master in CI run 41317061256. The old task-key/source-audit expectations were corrected for the new workspace. Remaining CI outcomes will be compared against the baseline rather than reported as fully green.

Runtime boundaries

The persistent host owns managed CLI PTYs. API HTTP work and native Task execution remain frontend-owned; saved conversations survive. Consumer desktop/web private histories are not automatically imported. Native provider process/protocol tests use local fixtures; live account authentication was not exercised.

Publication follow-up

Updated the host-adapter manifest and Git-source allow-list to the exact published core. The updated PR passes the host provenance guard and all ten native receipt tests. The subsequent native-receipt job failure is the unchanged Rust 1.99 deprecation in vendored iced_winit AtomicU64::fetch_update, already present on master. The first candidate's native conversation layout, native provider acceptance, Rustdoc, strict Clippy and supply-chain workflow pass. The Files-follow extracted-harness failure has the same missing configuration fields/method as the baseline.

Final test result

Final CI 41328765920 completes with 2,027 tests passing, six failures and three ignored tests. Every failure has the same geometry test name and assertion values as baseline CI 41317061256; there are no added failures. The real-command PTY close-role test passes, resolving the earlier local uncertainty. Both corrected task-key/shell-identity source audits pass. The outer OSC52 ownership harness rejects all five deliberate mutations, and the font integration suite passes 4/4. Final strict Clippy, dependency policy, Rustdoc, installer checks and Release build pass. Existing Files-harness and vendored deprecation failures remain explicitly documented.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-01T17:05:51.236776Z	6aa997c	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.