Skip to content

1.7.248.dev0 — persistent clipboard settings and interrupted-history archival

Pre-release
Pre-release

Choose a tag to compare

@groopcd groopcd released this 19 Nov 16:54
· 43 commits to master since this release

Highlights

  • Remember Ctrl+Y clipboard importing per workspace. Enable once with --host-clipboard; later native TUI clients inherit the choice.
  • Keep opt-outs explicit and durable. --no-host-clipboard saves disabled, and strict clipboard symlink settings survive disable/re-enable. Use oc-box preferences --host-clipboard on|off to change policy without launching or unlocking.
  • Archive interrupted history after verified shutdown. On eligible native OpenCode 2.3.x failures, oc-box can make one guarded post-stop archival attempt. Work is not resumed, and an interrupted turn still reports a nonzero result even when archival succeeds.

Usage

# Enable once for this workspace:
oc-box --project ~/devel/demo --host-clipboard

# Later clients inherit it:
oc-box --project ~/devel/demo

# Save disabled without opening a client:
oc-box preferences --project ~/devel/demo --host-clipboard off

Clipboard importing remains off when no choice is saved. Only the dedicated
host Ctrl+Y shortcut reads the clipboard; startup and preference changes never
read it. Saved policy contains booleans, not clipboard contents or helper paths.
Ordinary Ctrl+V/text paste and the independent host-drop preference are unchanged.

--no-host-clipboard-symlinks now saves strict capture for future clients;
--host-clipboard-symlinks explicitly restores ordinary symlink following.
Either startup option requires effective clipboard enable. The independent
preferences --host-clipboard-symlinks on|off setter can prepare that choice even
while importing is disabled. Normal file drops and live sharing remain strict.

Saved enable gracefully skips unavailable terminals/native V1/missing desktop
helpers without clearing the choice. Explicit enable still requires supported
native V2, a direct supported Konsole/Kitty terminal and its desktop helper.
An additional native TUI client can save/use the preference without restarting,
unlocking or refreshing the existing owner. Existing clients never live-toggle.
Fresh restores do not reactivate archived host clipboard policy.

Automatic history archival still requires verified whole-container shutdown,
the same workspace resources, and checked exports and imports. Explicit stop
can cancel recovery. A saved archive is not proof the interrupted work finished;
oc-box does not consume queued input or retry the work.

Validation and scope

The exact clean combined commit passed source and package CI on Python 3.10
and 3.13, native V1/V2 integration and native 2.3.x recovery fixtures
,
all seven distro dependency checks,
and the build-only publication gate
with Twine, isolated vault and tui checks, and exact artifact identity validation.

Source: 69a9ab2493754527cead47dcf192795d606d79ef,
absolute commit count 277, public version 1.7.248.dev0, full identity
1.7.248.dev0+g69a9ab2. The original full-history baseline remains 29.

The owner reviewed focused host results for history-fix commit
5135664,
including source, native binary and approved runner hashes:

  • Graceful: 31/31 checks passed; all 13 archives verified.
  • Stop-cancel: 29/29 checks passed; explicit stop prevented a restart or Reader launch.
  • Live transport: 31/31 checks passed; all 13 archives verified without consuming queued work or changing execution markers.

This is an experimental development prerelease, not stable promotion or
security certification. Those host results apply only to 5135664, not the
combined source. No new live desktop/native-composer or rootless-Podman
acceptance is claimed for persistent clipboard policy.

The existing manager limitations remain: UI full restore returned zero but the
later verifier refused manifest; intentional root-mode tightening is not proof
of all-entry equality or the sole cause. Portable UI was unarmed, and remaining
three-scope Storage, reviewed ciphertext deletion, source-removal preservation,
final journal/attestation and manager Quit checks remain unaccepted/unperformed.
Human observations remain NOT_AUTOMATICALLY_PASSED. Combined-browser validation
limitations documented in the 1.7 notes
also remain unchanged.

Stable master, its releases and PyPI files are unchanged. GitHub and PyPI are
the only publication targets for this release; LinkedIn automation is skipped.