Conversation
A note about dstack itself had nowhere to go except memory or a retro weeks later. /dstack-feedback <note> writes one file to the repo-level doc/dstack/feedback/ with status: new, the installed version/commit, and the project/command/ticket in flight — no question, no network, so logging costs nothing. Every ticket pick then gates pending notes right after the findings scan: filed as a GitHub issue on the dstack repo via gh (on the user's say-so, per note) or dropped with a recorded reason. Agents are told in every command to log friction the moment they hit it and never to file on their own. install.sh records repo= in .dstack-version so the command knows where to file (a fork stays a fork). dstack-retro reads feedback notes as a source. examples/feedback/ shows the shape of a dropped note. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NLMK6F3vQ1HzyU1Mxqt6Kr
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NLMK6F3vQ1HzyU1Mxqt6Kr
This was referenced Sep 12, 2026
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
Roadmap item 3 (
meta/roadmap-0.4.md). Based on #6; GitHub retargets tomasteronce #6 merges. Independent of #7 and #8 (if #8 also lands, the spec's principles list needs a one-line renumber — both add an "18.").harnesses/claude-code/commands/dstack-feedback.md, two modes:/dstack-feedback <note>— writes one file to repo-leveldoc/dstack/feedback/<date>-<slug>.mdwithstatus: new,kind, the installeddstack:version/commit, and acontext:line (project · command · ticket). Asks nothing, touches no network. Stops./dstack-feedback(no argument) — runs the gate: eachnewnote is filed as a GitHub issue (gh issue create --repo <repo>, only on the user's pick for that note) or dropped with areason:. "Sitting there" is not an outcome.dstack-ticketStep 3,dstack-yoloStep 2 (the one loop step that needs the human even at full autonomy; it never drops or files on its own), andSKILL.mdStep 0 on resume.dstack-ticket,dstack-yoloStep 7, anddstack-retroStep 4 (which also offers to turn each process observation into a note).install.shwritesrepo=into.dstack-version(from the checkout'sorigin, falling back to the canonical URL) so the command knows where to file; older installs fall back to the canonical repo.meta/process-notes.md(curated, cross-project).examples/feedback/shows a dropped note. README: walkthrough step 11, a Common-mistakes entry, an FAQ.Verification
bash -n install.sh;./install.shinto a scratch repo —dstack-feedback.mdlands,.dstack-versioncarriesrepo=https://github.com/dsegovia90/dstack.gh auth statuspasses here. No real issue was created during verification.🤖 Generated with Claude Code
https://claude.ai/code/session_01NLMK6F3vQ1HzyU1Mxqt6Kr