Feature: Async skill execution with deferred resolution
Resolved 💬 2 comments Opened Feb 27, 2026 by kevin-at-bunny Closed Mar 27, 2026
Summary
Allow slash commands/skills to execute asynchronously in the background while the user continues typing their prompt, resolving (blocking if needed) when the user submits.
Use Case
When loading a screenshot into context with a custom /ss skill:
Current behavior:
- Type
/ss - Wait for skill to execute (find file, read image)
- Type prompt
- Submit
Desired behavior:
- Type
/ss— starts executing in background - Continue typing prompt immediately
- Submit — blocks only if skill hasn't finished, otherwise proceeds
Why This Matters
Drag-and-drop currently feels faster than skills for file loading because it doesn't block input. The async model would make skills competitive with drag-and-drop for common workflows like pulling in screenshots, logs, or other context.
Suggested UX
- Visual indicator showing skill is loading (spinner in input area?)
- If user submits before skill completes, show brief "waiting for /ss..." message
- Skills that fail should surface error before prompt executes
Additional Context
This would be particularly valuable for I/O-bound skills (file reads, fetches) where the latency is noticeable but the user's typing time could overlap with execution.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗