Skip to content

[Web UX] complete rerun, reload recovery, file organization and multiple terminals #641

Description

@testikun

Problem

Follow-up to #639 and merged #640. OpenPI Web now has the main workbench tools, but continuous use still has gaps:

  • Editing an earlier prompt resends at the end instead of rerunning from that native history point; users need regeneration and an explicit route back to the original conversation.
  • Reload loses historical reading anchors and tool positions even when the exact Session remains available.
  • Workspace files lack complete rename, move, recoverable trash and folder import paths.
  • The workbar launcher permits only one terminal, and General settings show several uneditable summaries.
  • Session row controls remain visible on touch layouts instead of revealing on hover or focus.

Expected behavior and acceptance

Reuse Pi's native fork, prompt admission, exact Session authority and filesystem write lanes. Preserve the original conversation, file contents and unrelated local work. Store only bounded presentation bookmarks in browser storage, and reacquire native resources from their owners.

Provide independent terminals with per-tab input, output, names, reconnect and close; the plus button opens the complete launcher. Make existing result-display/footer choices editable through the canonical configuration, and route agent choices through /openpi-setup.

Validate native lifecycle facts, store/UI recovery and actual Chromium operation separately, including rejection, refresh, identity conflicts and narrow layouts. Run bun run check, bun run test and production browser regressions on current main (Pi 0.99.1). Record ablations and unverified platform boundaries. No additional model/provider stack or workflow router.

References

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions