add starter sessions to workspace templates

Materialize first-load template sessions from portable blueprint config and render their seeded messages without copying runtime history. Replace the deeplink template import handoff with a dedicated start-with-template modal that creates a workspace from a chosen folder.
This commit is contained in:
Benjamin Shafii
2026-03-24 22:17:25 -07:00
parent 21a26ef580
commit 7e7666bd55
12 changed files with 865 additions and 17 deletions

View File

@@ -71,6 +71,7 @@ Agents, skills, and commands should model the following as OpenWork server behav
- writes to `.opencode/`, `opencode.json`, and `opencode.jsonc`
- OpenWork workspace config writes (`.opencode/openwork.json`)
- workspace template export/import, including shareable `.opencode/**` files and `opencode.json` state
- workspace template starter-session materialization from portable blueprint config (not copied runtime session history)
- share-bundle publish/fetch flows used by OpenWork template links
- reload event generation after config or capability changes
- other filesystem-backed capability changes that must work across desktop host mode and remote clients