mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-09-23 11:20:13 +00:00
4b9b8bcbb9
* feat(telemetry): record what kind of exception ended a flow Flow failures are visible but undiagnosable. Live data shows roughly 17% of flows ending in outcome=failed, and 72% of AgentExecutor failures completing in under 200ms - far too fast to be an LLM call - but nothing records what the failure actually is, so there is no way to tell a real defect from a user pressing Ctrl-C. Record the exception's class name as error_type on Flow Completed and Flow Method Failed. The class name only: str(error) is never read, because it routinely carries prompts, model output, file paths and credentials. The isidentifier() check is the allowlist that enforces it - any message text reaching that argument carries a space or punctuation and is dropped - and it lives inside Telemetry rather than at the call site so a future caller cannot bypass it. Method names and flow state remain unrecorded. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ASfWmW3RGy4qAQm6s8U9jH * docs(frontend): point the frontend guides at their edge paths The frontend guides added in #6686 exist only under edge - they are not in any frozen version snapshot - but their 80 internal links use the bare /en/guides/frontend/... form, which resolves against the released versions where those pages do not exist. mint broken-links fails on every one of them, which blocks every open PR, not only the one that added them. Use the /edge/en/... form the repo already uses for other edge-only pages (concepts/streaming, learn/execution-boundary-hooks). Anchors are preserved. No page content changes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ASfWmW3RGy4qAQm6s8U9jH --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
69 lines
2.9 KiB
Plaintext
69 lines
2.9 KiB
Plaintext
---
|
|
title: Reasoning
|
|
description: Show the model's thinking in the chat automatically, with no component to build.
|
|
icon: brain
|
|
mode: "wide"
|
|
---
|
|
|
|
## Thinking, rendered for free
|
|
|
|
When a reasoning-capable model thinks before it answers, CopilotKit renders that thinking right in the chat. This is the simplest generative-UI pattern in the whole section: there is nothing to build. No hook, no component, no props. Use a reasoning-capable model, keep the streaming wrapper your Flows already have, and the chat surface from the [Overview](/edge/en/guides/frontend/overview) does the rest.
|
|
|
|
## Use a reasoning-capable model
|
|
|
|
Reasoning is surfaced automatically by `copilotkit_stream`, which every Flow example already wraps the model call in. The bridge reads the model's reasoning deltas and emits them to the frontend. It is provider-agnostic and works over both of CrewAI's streaming transports, so the only thing you change is the model.
|
|
|
|
```python
|
|
# recipe_flow.py
|
|
from crewai.flow.flow import Flow, start
|
|
from ag_ui_crewai.sdk import copilotkit_stream, CopilotKitState
|
|
from litellm import acompletion
|
|
|
|
|
|
class RecipeFlow(Flow[CopilotKitState]):
|
|
@start()
|
|
async def chat(self):
|
|
response = await copilotkit_stream(
|
|
acompletion(
|
|
# any reasoning-capable model, e.g. deepseek-reasoner
|
|
model="deepseek/deepseek-reasoner",
|
|
messages=self.state.messages,
|
|
stream=True,
|
|
)
|
|
)
|
|
message = response.choices[0].message
|
|
self.state.messages.append(message)
|
|
```
|
|
|
|
Models that emit reasoning over the standard channel include DeepSeek `deepseek-reasoner`, Anthropic extended thinking (Claude), and Gemini thinking, among others. Swap the `model` for one of these and its thinking starts streaming through.
|
|
|
|
This works the same for both Crews and Flows, since both run their model calls through `copilotkit_stream`.
|
|
|
|
## Render it
|
|
|
|
There is no frontend step. The `CopilotChat`, `CopilotSidebar`, or `CopilotPopup` surface you already mounted shows the reasoning as it streams, above the answer it produced.
|
|
|
|
```tsx
|
|
import { CopilotChat } from "@copilotkit/react-core/v2";
|
|
|
|
<CopilotChat agentId="recipe" />
|
|
```
|
|
|
|
<Note>
|
|
There is no `useReasoning` hook and no reasoning component to write. Reasoning is not something you wire up on the frontend; it renders automatically as long as the model emits it.
|
|
</Note>
|
|
|
|
## Related
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Generative UI" icon="wand-magic-sparkles" href="/edge/en/guides/frontend/generative-ui">
|
|
The full spectrum, from author-controlled to agent-invented UI.
|
|
</Card>
|
|
<Card title="Agentic Generative UI" icon="list-check" href="/edge/en/guides/frontend/agentic-generative-ui">
|
|
Render live agent state as the Flow works.
|
|
</Card>
|
|
<Card title="Frontend Overview" icon="browser" href="/edge/en/guides/frontend/overview">
|
|
Set up the chat surface and runtime.
|
|
</Card>
|
|
</CardGroup>
|