Repository navigation
The editor follows every run of the commander - #55
Merged
Merged
Conversation
StepIt Commander publishes the whole run on /stepit_server/execution, and the StepIt Editor shows it in an Execution tab, whoever started it. Co-Authored-By: Claude Opus 5.5 <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.
Points the modules at their PRs:
/stepit_server/execution.The README and
CLAUDE.mdmention the topic and the tab.rig.yamlis unchanged: the editor follows/stepit_server/executionby default.Checked on this PC's rig, with fake motors: a run from the command line shows in the editor without leaving the Editor tab; a page reloaded mid-run shows it at once; a run from the editor still stops.
Merge the two module PRs first; this pointer then moves to their merge commits.
🤖 Generated with Claude Code