- Check process_running and ready state before making inference request
- Emit descriptive error messages for each failure scenario
- Handle local vs remote connection modes appropriately
- Validation score: 100 (was 0)
Result: {"status":"keep","validation_score":100,"response_time_ms":500}
Deliver a Forge-branded Manus-like agentic transcript inside the main chat UI. Separate thinking, execution progress, system progress notes, and final response. Add a Tauri event bridge so agentic steps can update in real time without breaking normal chat mode.
<acceptance_criteria>
Agentic mode shows a dedicated thinking/plan card immediately after the user prompt.
Step execution updates stream into the active chat as progress changes.
Intermediate system updates render as dense dark rows without classic assistant bubble chrome.
Final response renders as a clean text block with code-copy support and artifact action area.
Normal chat mode remains unchanged for non-agentic replies.
New behavior is covered by focused tests for formatting/render gating.
</acceptance_criteria>
<implementation_plan>
Create chat-native agentic UI blocks (AgentThinkingCard, AgentStepList, AgentSystemMessage, AgentFinalResponse) and refactor ForgeAgentBubble to compose them.
Extend forgeagent types to support transcript-level system messages and artifact CTA metadata needed by the new UI.
Integrate agentic rendering into ChatView with conditional transcript blocks and Manus-like assistant presentation.
Add a Rust→Tauri event contract for plan and step progress; wire frontend listeners to update live agentic state.
Add targeted tests and update .planning/STATE.md / summary files after verification.
</implementation_plan>
- `pnpm exec vitest run` for the new/updated agentic tests
- targeted Rust build/test for event contract if touched
- manual `pnpm tauri dev` verification of agentic transcript layout
Evandro Fonseca Junior
77c57c3d45