chihlasm/resolutionflow
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[Feature] Command Output Capture #57

New Issue
Closed
opened 2026-02-10 15:58:51 +00:00 by chihlasm · 0 comments
chihlasm commented 2026-02-10 15:58:51 +00:00 (Migrated from github.com)
Copy Link

Summary

Action nodes (which show commands to run) get an optional "Paste Output" text area. Engineers run commands, copy output, paste it in. Output is captured in session data and included in exports.

Why

  • Engineers already run commands and read output during troubleshooting
  • Today the output is lost — exports say "ran this command" but not what it returned
  • Captures evidence that proves work was done and documents the state of the system
  • Pairs with scratchpad for complete evidence capture

Export Output Example

> Ran: Get-Service -Name Spooler
> Output:
>   Status: Stopped
>   Name: Spooler
> Decision: Service was stopped, proceeded to restart

Implementation Notes

  • Add optional command_output field to session decision JSONB
  • Add collapsible text area below commands on action nodes in TreeNavigationPage
  • Include in export with code formatting (monospace/code block)
  • Future: syntax highlighting for PowerShell, JSON output formats
  • Future: image paste for screenshots of GUI-based evidence

Acceptance Criteria

  • Collapsible "Paste Output" textarea on action nodes with commands
  • Command output saved to session decision record
  • Output included in all export formats with code formatting
  • Output visible in session detail/review page

Sources

  • docs/plans/2026-02-04-feature-ideas-brainstorm.md — Idea 3: Command Output Capture

Priority

Do Next — small effort, enriches every export

## Summary Action nodes (which show commands to run) get an optional "Paste Output" text area. Engineers run commands, copy output, paste it in. Output is captured in session data and included in exports. ## Why - Engineers already run commands and read output during troubleshooting - Today the output is lost — exports say "ran this command" but not what it returned - Captures evidence that proves work was done and documents the state of the system - Pairs with scratchpad for complete evidence capture ## Export Output Example ``` > Ran: Get-Service -Name Spooler > Output: > Status: Stopped > Name: Spooler > Decision: Service was stopped, proceeded to restart ``` ## Implementation Notes - Add optional `command_output` field to session decision JSONB - Add collapsible text area below commands on action nodes in TreeNavigationPage - Include in export with code formatting (monospace/code block) - Future: syntax highlighting for PowerShell, JSON output formats - Future: image paste for screenshots of GUI-based evidence ## Acceptance Criteria - [ ] Collapsible "Paste Output" textarea on action nodes with commands - [ ] Command output saved to session decision record - [ ] Output included in all export formats with code formatting - [ ] Output visible in session detail/review page ## Sources - `docs/plans/2026-02-04-feature-ideas-brainstorm.md` — Idea 3: Command Output Capture ## Priority **Do Next** — small effort, enriches every export
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
10x-analysis
From 10x product analysis
 backend
FastAPI/Python work
 bug
Something isn't working
 collaboration
Team sharing, escalation, notifications
 database
PostgreSQL/schema changes
 documentation
Documentation updates
 duplicate
This issue or pull request already exists
 enhancement
Improvement to existing feature
 feature
New functionality
 frontend
React work
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 integration
PSA, external service integrations
 intelligence
Analytics, AI, data-driven features
 invalid
This doesn't seem right
 priority: high
Do this soon
 priority: low
Nice to have
 priority: medium
Important but not urgent
 question
Further information is requested
 quick-win
Low effort, high value
 strategic
Long-term strategic bet
 ux
User experience improvements
 wontfix
This will not be worked on
No Label 10x-analysis backend feature frontend priority: high
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
chihlasm
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#57
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?