Show agent thinking and tool calls in the chat UI
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 22/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Da chiarire
- Stato di attività
- Ferma
- Stack tecnologico
- python, typescript
Direzione di ricerca
Start with apps/app/src/components/tool-rendering.tsx and inspect the existing ToolReasoning and useDefaultRenderTool integration. Then read apps/agent/main.py to understand how agent events are emitted; the work is done when thinking and tool activity can be presented as a coherent, collapsible chat view with the proposed status details.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
Surface the agent's thinking process and tool call activity in the chat UI so users can see how the agent reasons, not just the final answer.
Current State
- Tool calls: The
ToolReasoningcomponent (apps/app/src/components/tool-rendering.tsx) already renders tool names, arguments, and status (executing → complete) viauseDefaultRenderTool. This is a good foundation but is minimal — it shows what tool was called, not why. - Thinking/reasoning: Not shown at all. The agent's intermediate thought process is invisible to the user. There is no UI for streaming thinking tokens or displaying step-by-step reasoning.
Proposal
1. Agent thinking display
Show the agent's reasoning as it works through a problem. This could be:
- Streaming thinking tokens — If using a model with extended thinking (e.g. Claude with
thinkingblocks), render these in a collapsible "Thinking…" section above the response. Show the thinking text streaming in real-time with a subtle visual treatment (muted text, indented, or in a distinct container). - Step-by-step reasoning — For multi-step agent tasks, show each reasoning step as the agent progresses (e.g., "Analyzing your request…", "Looking up existing todos…", "Organizing by priority…").
2. Enhanced tool call visualization
Build on the existing ToolReasoning component:
- Execution timeline — When multiple tools are called in sequence, show them as a vertical timeline so users see the agent's workflow.
- Tool results — Show a summary of what the tool returned (e.g., "Found 3 todos" or "Updated 2 items"), not just the arguments passed in.
- Duration — Show how long each tool call took.
- Grouped display — Collapse completed tool calls into a compact summary, expand only the active one.
3. Thinking + tools combined view
When the agent thinks, then calls a tool, then thinks again — show this as a coherent narrative:
🧠 Thinking: "The user wants to organize their todos by priority..."
🔧 get_todos → returned 5 todos
🧠 Thinking: "I'll group these into high/medium/low priority..."
🔧 manage_todos → updated 5 todos
✅ "I've organized your todos by priority!"
Implementation Notes
- CopilotKit's
useDefaultRenderToolalready provides the hook point for tool rendering - The agent backend (
apps/agent/main.py) would need to emit thinking/reasoning events — this could be done via LangGraph's streaming callbacks or by adding thinking state toAgentState - For models with native thinking (Claude extended thinking), CopilotKit may already surface thinking tokens — needs investigation
- The
ToolReasoningcomponent atapps/app/src/components/tool-rendering.tsxis the starting point for enhanced tool visualization
Design Considerations
- Thinking should be collapsible by default after completion — users who want transparency can expand it, but it shouldn't clutter the chat for those who don't
- Tool calls should feel like a progress indicator, not noise — compact when done, detailed when active
- The overall effect should make the agent feel more trustworthy and transparent without overwhelming the UI
- Lingua principale
- TypeScript
- Stelle
- 1.6k
- Fork
- 202
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di CopilotKit/OpenGenerativeUI
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
CopilotKit/OpenGenerativeUI#87 · 2 commenti ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
Tutte le issue di CopilotKit/OpenGenerativeUI
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
ontola/atomic-server#1625 ·
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
-
bug via-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
midnightntwrk/midnight-sdk#403 ·