Add TODO entry: execute Snips with per-CLI shell and run history#11
Merged
Conversation
Snipdeck today only constructs commands and copies them. The user wants to also execute them: each CLI declaring its shell (cmd / PowerShell / pwsh / bash), live output streaming into the Snipdeck chrome, and a searchable per-Snip execution history. Captures the sketch, the storage trade-off (the existing "one JSON document" rule was scoped to definitions, not arbitrary observation data — so SQLite specifically for execution history is worth a real conversation), and the open questions (working dir, env vars, safety confirmation, ANSI handling, large-output capping). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
A CLI's executable location is useful execution context but must not be mandatory — Snipdeck has to remain a sensible place to author Snips for a CLI that isn't installed yet on this machine. Document that the field is optional, validated only at Run time, and that the working directory defaults sensibly off the executable when set. Drops the working-directory open question since it's now part of the sketch. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The user explicitly wants: - Custom environment variables per CLI (with Snip-level override). Non-secret values stored in the JSON document verbatim; secret values stored via Windows DPAPI (current-user scope). This flips the parked 'secret / masked parameters' item to 'needed' and accepts the cross-machine-sync trade-off (you re-enter secrets per machine — the alternative is plaintext in a synced document, which is wrong). - Free-form labels on each execution, e.g. support ticket IDs. Labels are searchable from the history view, settable in the Run dialog, editable post-hoc on past runs, and — the productivity unlock — pinnable from the shell so every Run during an incident is auto-tagged. Updates the execution-history record to include Labels and drops the environment-variables open question since it's now part of the sketch. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan
🤖 Generated with Claude Code