Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix: resolve blox workspace provisioning and ACP issues#38

Merged
wesbillman merged 2 commits intomainfrom
fix/blox-workspace-issues
Feb 11, 2026
Merged

fix: resolve blox workspace provisioning and ACP issues#38
wesbillman merged 2 commits intomainfrom
fix/blox-workspace-issues

Conversation

@wesbillman
Copy link
Collaborator

@wesbillman wesbillman commented Feb 11, 2026

Summary

  • ACP over Blox: Replaced the naive blox ws prompt approach with proper ACP protocol proxied through blox acp <workspace>, enabling full session/timeline support for remote branches
  • Working dir fix: Remote agents no longer receive the local macOS path (e.g. /Users/.../builderbot) in ACP session requests — sends "." so the remote agent uses its own workspace directory
  • Blox status deserialization: Handle integer status codes from blox ws info/blox ws list (was expecting strings, causing parse failures)
  • SSH → HTTPS source URL: Convert [email protected]:... to HTTPS before passing to blox ws start (blox needs a fetchable URL)
  • Goose args fix: Split --with-builtin developer,extensionmanager into separate flags per CLI convention
  • RemoteBranchCard rewrite: Replaced bespoke prompt UI with timeline + session modal pattern matching local BranchCard
  • Cleanup: Removed dead send_workspace_prompt command and ws_prompt function

Test plan

  • Create a remote Blox workspace branch and verify it provisions successfully
  • Confirm the remote agent reports its own workspace path (not the local path) when asked
  • Verify timeline, commits, and notes work on remote branches
  • Verify local branches are unaffected by the ACP working dir change
  • Test workspace status polling transitions (starting → running)

🤖 Generated with Claude Code

wesbillman and others added 2 commits February 11, 2026 13:02
Three fixes for remote workspace support:

1. Resolve local repo path to HTTPS remote URL before passing to
   `blox ws start` (blox cannot fetch from local filesystem paths,
   and SSH URLs are also unsupported).

2. Handle integer status codes in blox JSON output — the CLI returns
   status as a numeric enum (e.g. 3 = running) rather than a string.
   Added a custom deserializer that accepts both formats.

3. Split goose --with-builtin args so each gets its own flag, avoiding
   the comma-in-value conflict with blox's comma-separated --command
   format.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
When running through `blox acp`, the local working_dir (e.g.
/Users/.../builderbot) was being sent in ACP NewSessionRequest and
LoadSessionRequest. The remote agent would report this non-existent
path as its working directory. Now AcpDriver tracks `is_remote` and
sends "." instead, so the remote agent resolves its own workspace path.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@wesbillman wesbillman force-pushed the fix/blox-workspace-issues branch from cd7111e to 30f7936 Compare February 11, 2026 21:03
@wesbillman wesbillman merged commit 7ca03d0 into main Feb 11, 2026
2 checks passed
@wesbillman wesbillman deleted the fix/blox-workspace-issues branch February 11, 2026 21:04
loganj added a commit that referenced this pull request Feb 26, 2026
Seed recent activity from filesystem on startup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants