warp/launch_configurations/*.yaml not symlinked into ~/.warp/launch_configurations/ by setup #10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-20T08:24:22Z - https://github.com/coilysiren/agentic-os/issues/106
Symptom. New entries in
warp/launch_configurations/*.yamldon't reach Warp until an operator manuallyln -s's them into~/.warp/launch_configurations/. Existing entries likeclaude-luca.yamlwere symlinked by hand at some point in the past; new ones added since (e.g.claude-dispatch-interactive.yaml, just landed in this repo) are invisible to Warp until the same hand step.No
claude-dispatch-interactive.yamlsymlink. The file lives in the repo, Warp doesn't see it.Why this matters.
coily dispatch interactive <ref>(coilysiren/coily#270) depends on the launch config being live in~/.warp/launch_configurations/. The interactive smoke test will fail at theopen warp://launch/claude-dispatch-interactivestep until the symlink is in place, and the soft-fallback ("paste this in a new tab") won't make it obvious that the cause was a missing symlink rather than a broken config.Fix shape. Add a setup pass (sibling to
agentic-os-kai/setup.sh's~/.claude/skills/walk) that walkswarp/launch_configurations/*.yamlhere and symlinks each file into~/.warp/launch_configurations/<basename>.yaml. Idempotent. Sweeps dangling symlinks the way the skills walk already does. Possible homes:setup.shat the root ofcoilysiren/agentic-osthat owns Warp config plumbing (settings.toml symlinks, themes, launch_configurations).coilysiren/agentic-os-kai/setup.sh's walk so a single bootstrap script covers both Claude skills and Warp configs.Either is fine. The "two scripts, one per repo" shape is cleaner since this repo is the canonical owner of the source files, and agentic-os-kai is the canonical aggregator for Kai-specific config — but the per-host plumbing convention has been agentic-os-kai's setup.sh so far.
Routed here rather than coily because the source files live in this repo. Per coilysiren/coily#270 the seam between coily and agentic-os is exactly two strings; the symlinking responsibility belongs on this side of the seam.