Repository navigation
Description
Dependencies
- Marketing promise on https://bowire.io / comparison table currently reads
Git-native workspace -> planned. Bruno's.bruconvention is the bar.
Kuestenlogik.Bowire.Endpoints.BowireWorkspaceEndpoints already mounts a .bww workspace file in the current directory that bundles urls, environments, globals, collections. The 'planned' marketing claim is therefore partly shipped -- the rest of the per-project state still lives under ~/.bowire/ (global per-user) and doesn't migrate cleanly into git.
To close the gap so 'Git-native workspace' becomes a clean ✓ on the comparison page:
- Recordings -- migrate
~/.bowire/recordings.jsoninto the workspace file (or reference a sibling.bwrper recording so each one diffs cleanly in PR review). Today recordings are user-scoped; team workflows want them committed alongside the code that drives the captures. - Flows -- the visual-flow editor (flows.js, 1527 LOC) persists to user-scope storage. Same migration as recordings.
- Plugin pins -- a workspace should declare 'this project expects these protocol plugins at these versions'. The standalone host can warn on mismatch / offer to install on open.
- Stable serialization -- pretty-printed JSON with deterministic key ordering so diffs stay clean across saves. Consider line-per-entry formatting for lists so review highlights the actual change.
- Schema / format version --
workspaceFormatVersionfield so future changes can be detected and migrated gracefully. - Workspace-scope vs user-scope split in the UI -- workbench Settings should distinguish 'this project's setup' from 'my preferences' so a team member opening the workspace doesn't inherit personal preferences.
- Marketing claim follow-through -- once the above lands, update the comparison row from 'planned' to '✓' and remove the 'see the roadmap' note from the Bruno-comparison paragraph.
Why P2 not P1: .bww already covers the highest-friction items (urls / environments / collections) that teams hit first. The remaining bits (recordings, flows, plugin pins) are valuable but not blocking real adoption today.
Tracked board-level. Likely lands in two passes: format extension first (recordings + flows), then UI surfacing.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
[-]Workspace: complete the Git-native story ( file)[/-][+]Workspace: complete the Git-native story (.blw file)[/+]chore(planning): theme-driven milestones + drop redundant "Later" mil…
chore(planning): split v1.9 into v1.9 (AI for security) + v1.10 (gRPC…
feat: #144 Phase 1.8 — disk-only storage mode + manifest-only loading…
thomas-stegemann commentedon Jun 10, 2026
Status after wide audit (2026-06-10)
.blwworkspace-file skeleton inBowireWorkspaceEndpoints.cs. Open for the git-native story: stable per-entity-file serialisation (#148), recordings inclusion with chunked layout (#144), flows persistence, plugin pins (which protocol plugins the workspace needs), format-version field, UI for workspace selection / creation.chore(roadmap): split v2.0/v2.1, add v2.2/v2.3/v2.4/v2.5 pillars
feat(workspace): #58 Phase 1 — extend .blw schema with version + reco…
thomas-stegemann commentedon Jun 12, 2026
Phase 1 shipped in 2f80024 —
.blwschema extended withworkspaceFormatVersion,recordings,flows, andpluginPins; backwards-compatible deserialization, stable camelCase serialization with deterministic key order. 9 round-trip + backwards-compat tests pass.Phase 2 (UI wiring, plugin-pin check on open, scope split, marketing-claim follow-through) tracked in #193 → v2.1.
[-]Workspace: complete the Git-native story (.blw file)[/-][+]Workspace: complete the Git-native story (.bww file)[/+]