Repository navigation
oc-box v1.7.223.dev0 — combined development update
Pre-releaseExperimental development update
This prerelease combines the card-dashboard, retained-subagent history-recovery,
and native/web attachment work on devel. Stable v1.6.94 / master remain
unchanged. This is not stable UI acceptance or a security certification.
What changed
- Native TUI image/PDF drops, enabled by default per workspace. Supported
direct Konsole/Kitty clients can import qualifying pasted image/PDF paths
without model tool calls or per-file confirmation.--no-host-dropsaves an
opt-out;--host-dropsaves enabled and strictly requires compatibility.
oc-box preferences --host-drop offchanges policy without opening another
client. Existing clients keep their current setting. - Correct web conversation and all open TUI tabs. A first-party tabstrip
surrounds one unmodified native iframe. Fresh cooperative TUI reports provide
the exact owning-TUI conversation and ordered open roots, including idle tabs.
web --session IDwins explicitly. Children retain their exact route and
native read-only behavior; root highlighting is separate. Older running owners
require explicit selection until a subsequent normal owning startup loads the
helper; attach never refreshes configuration or credentials. - Optional browser attachments.
oc-box web --attachmentsadds trusted File
drops and a chooser to that same native view. The native composer owns draft
handling and Send. No prompt is submitted automatically. - Responsive card dashboard. Navy/cyan host resource cards, workspace
context/inspector, inline session-only settings, compact switches and larger
clear-control hit targets retain the existing explicit operations, clipboard
and private-input boundaries. No new resource-control RPCs or telemetry. - Native 2.3.0 retained-subagent history fallback. The live owner still
refuses pending jobs. Checked persisted history may be recovered only after
verified shutdown through the existing guarded reader. The original warning
and nonzero result remain; jobs are not resumed, acknowledged or declared
completed.
Important disclosure and compatibility notes
A qualifying complete image/PDF pathname paste anywhere in an
importing-enabled native TUI authorizes capture, not just a physical drag into
the composer. Disable importing when that policy is inappropriate. The separate
confirmation-based attach --broker workflow remains available.
Konsole remains pathname-paste-only, with unchanged child output and no OSC 72
probes. Only the known Kitty profile reserves its audited structured-drop traffic.
TUI limits are 8 MiB/file, four files/16 MiB per batch and 32 files/64 MiB per
client. Browser limits are 20 MiB/file, eight files/40 MiB per drop.
PNG/JPEG/GIF/WebP/PDF are supported within their respective guards; DOCX
conversion is not provided. Model support varies.
Staging, native/browser history, provider processing, copies and backups can
retain disclosed bytes. Cleanup is best-effort, not recall or per-session
filesystem isolation. Mainline OpenCode remains unmodified; the native TUI,
server, tools, MCPs and plugins remain container-side.
Validation and known limitations
- Application runtime bytes match the fully green
9c614f7integration:
Python 3.10/3.13 source/package CI, native V1/V2 and 2.3.0 history checks, and
all seven distro jobs. The full local matrix ran 2,405 cases per interpreter
without failures (six skips on 3.10, three on 3.13); eight focused native
TUI/helper/web checks passed across unmodified 2.2.6/2.3.0. - The final combined rendered-browser gate remains incomplete. Earlier
explicit-selection Chromium checks passed 69 checks per native version on
eff0c60; later real-helper attempts established automatic non-first owner
selection and four actual ordered roots but remained partial. A subsequent
private PTY/watchdog timeout yielded no durable phase results. No final browser
pass or unforced cleanup is inferred from that attempt, and old results are
not promoted to this release. - Historical dashboard restore acceptance is still incomplete: UI full
restore returned 0, but its later integrity verifier refusedmanifest.
Portable UI was unarmed; remaining three-scope Storage, reviewed ciphertext
deletion, source-removal/preservation, final journal/attestation and manager
Quit checks remain unperformed or unaccepted. - No new physical Konsole/Spectacle/Kitty gesture, rootless-Podman lifecycle,
real-provider, comprehensive fault/race or security acceptance is claimed.
Earlier host reports retain their original source identities and scopes.
See the combined release notes and limitations
and command reference.
Upgrade
After publication completes, existing channel-aware installations can use:
oc-box upgrade --develGitHub and Python-package installation owners remain distinct. No workspace
reset, history reimport or credential-policy change is required. Running clients
and existing host installations are not live-updated by publishing this release.
Source identity
- Tag / public package:
v1.7.223.dev0/1.7.223.dev0 - Full CLI/resource identity:
1.7.223.dev0+g65bae6b - Commit:
65bae6bc1524557b818243a08212ae1f59884f4b - Absolute commit count:
252; original baseline:29 - Channel: development (
devel), not stable
Only the guarded publishing workflow's validated wheel/sdist, identity and
checksums are release artifacts. Development publication does not authorize a
LinkedIn post; any automatically generated announcement is preview-only.
LinkedIn highlights
- A fresh TUI 2.0 experience
- Screenshots, PDFs and shared web tabs
- Smoother workflows. Better history recovery.
LinkedIn post
oc-box 1.7.223.dev0 · development preview — experimental
Meet the new oc-box TUI 2.0: a fresh look, a clearer workspace, and less friction between you and your next idea.
This development update brings together:
• A redesigned TUI 2.0 dashboard with responsive cards, a workspace overview, and simpler everyday controls.
• New ways to bring screenshots, images, and PDFs into your native TUI and web workflows—so sharing context takes less effort.
• Your open TUI conversations in the web interface, with easier switching and a clearer view of where you’re working.
• More control over native file importing, with a saved setting for each workspace.
• Improved conversation-history recovery, helping you pick up where you left off.
• Smoother navigation, better draft continuity, and a collection of everyday usability fixes.
All around unmodified OpenCode, with your tools and integrations running together in a rootless Podman workspace.
Less context switching. More flow.
Explore the new interface and tell us what you think.
This is a development prerelease, not a stable recommendation.
Release notes: https://github.com/groopcd/oc-box/releases/tag/v1.7.223.dev0
#OpenSource #Linux #DeveloperTools #OpenCode #Podman