GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — WorkspaceBuilder: add an opt-in parallel builder · Issue #1062 · tmux-python/tmuxp

WorkspaceBuilder: add an opt-in parallel builder #1062

New issue
Copy link
New issue
Copy link
Open
Open
WorkspaceBuilder: add an opt-in parallel builder#1062
Copy link
Labels
WorkspaceBuilderenhancement

Description

@tony
tony
opened on Jun 27, 2026
Issue body actions

Summary

Add a separate opt-in builder that prioritizes faster workspace construction while keeping the classic builder as the compatibility default.

Related: #1053, #1054, #1056, #1058.

Proposed behavior

  • Implement a parallel builder selected explicitly through the builder mechanism introduced in the base work.
  • Keep the classic builder as the default for existing workspaces and dependency-sensitive configurations.
  • Allow the parallel builder to create pane/window structure and observe readiness with less serialized waiting where the builder contract allows it.
  • Document that pane commands are not guaranteed to prepare later pane split-time inputs such as start_directory, shell, window_shell, pane environment, or other split-time state.
  • Recommend classic builder behavior or earlier setup phases such as before_script / shell_command_before for configs that rely on strict side effects.
  • Keep this separate from the experimental chain-builder work while allowing the protocol to learn from Experimental: pure-chain ChainWorkspaceBuilder + --builder=chain #1054.

Acceptance criteria

  • The parallel builder is opt-in and not selected by existing workspace files.
  • Tests cover faster grouped creation behavior and the documented relaxed dependency guarantees.
  • Compatibility-sensitive ordering remains covered by classic-builder tests.
  • Documentation explains when to choose classic versus parallel behavior.

Activity

  1. tony
    added
    enhancement
    WorkspaceBuilder
    on Jun 27, 2026
  2. tony
    added a parent issue on Jun 27, 2026
    • Workspace builder roadmap: classic default, pluggable builders, readiness policy, and parallel loading #1058
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    WorkspaceBuilderenhancement

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.