Support rich inline content within ProgressStep for reasoning traces
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start by inspecting the chatbot extension's use of ProgressStepper, ProgressStep, popoverRender, and ExpandableSection, then compare the requested inline rich-content behavior with the existing @patternfly/react-core API. The issue does not name files or tests; done would require an agreed component design that supports inline reasoning, evidence, structured data, and expandable details within each step.
Written by the indexing model from the issue text.
Description
Summary
ProgressStepper (in @patternfly/react-core) shows step names and statuses but isn't designed for rich content within each step. While ProgressStep accepts children (ReactNode), the layout renders children as the step title — it's not built for content blocks like reasoning text, structured data, or expandable evidence.
AI Chain of Thought patterns need a stepper-like component where each step can contain inline rich content: the reasoning text for that phase, evidence or data the AI examined, and expandable detail. A hybrid of ProgressStepper structure with ExpandableSection content within each step would address this.
popoverRender partially helps but puts content in a popover rather than inline.
Use case
A background agentic task (installation, upgrade, multi-step automation) where each phase shows not just "Analyzing logs ✓" but the actual analysis output inline — what the AI examined, what it found, and what it concluded at each step.
Context
This gap was identified during review of the Chain of Thought AI UX standard (Red Hat UXD, AUX-140). Note: ProgressStepper itself lives in patternfly/patternfly-react, but this issue is filed here since the use case is AI-driven and may be better addressed by the chatbot extension.
Jira Issue: PF-4692
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 38
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from patternfly/chatbot
-
ChatbotWelcomePrompt: long prompt title and message overflow suggestion cardsPossibly taken @rebeccaalpert claimed this 10 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
patternfly/chatbot#910 · 3 comments · 1 assignee ·
-
PF Team
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
patternfly/chatbot#852 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
patternfly/chatbot#918 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
patternfly/chatbot#916 ·
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
patternfly/chatbot#915 ·
All issues in patternfly/chatbot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Doist/todoist-cli#576 ·
Maintainers usually reply within 1 day
-
feature
Difficulty 1/5 Under an hour Newbie friendliness 72/100
vercel-labs/skills#2370 ·
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CopilotKit/aimock#491 ·
Maintainers usually reply within 1 day