* Title: Fix WorkflowFailedEvent error extraction to use details instead of error Body:
Summary
Fixed WorkflowFailedEvent mapping to extract error message from details.message instead of non-existent error attribute
Added support for including details.extra context in error messages when present
Problem
The WorkflowFailedEvent handler in _mapper.py was reading event.error, but WorkflowFailedEvent uses a details attribute (of type WorkflowErrorDetails), not error. This caused all workflow failures to display "Unknown error" in the UI instead of the actual error message.
Fix
Updated the handler to match the pattern already used by ExecutorFailedEvent:
Read from event.details instead of event.error
Extract details.message for the error text
Include details.extra context when available
* improve error handling consistency
* Provide way for HITL with magentic
* support tool call approvals and hitl stall replan
* human plan intervention sample
* Clean up
* Improve loging
* updates
* Add type annotations for AgentRunEvent and AgentRunUpdateEvent data attributes
* Fix unnecessary cast after typing improvement
* Mcp pkg update introduced type change. Fix it.
* update opentelemetry deps to 1.39.0 and use LogRecordExporter for type compatibility
* show app version in devui .NET: Python: Improved Versioning for DevUI
Fixes#2059
* feat: Add multimodal input support for workflows and refactor chat input
This PR adds support for multimodal content (images, files) in workflow
inputs and refactors the chat input into a reusable component.
## Multimodal Workflow Support
- Add `isChatMessageSchema()` to detect ChatMessage input schemas
- Update `RunWorkflowButton` to use `ChatMessageInput` for ChatMessage workflows
- Wrap multimodal content in OpenAI message format for backend processing
- Add `_is_openai_multimodal_format()` to detect OpenAI ResponseInputParam
- Update `_parse_workflow_input()` to route multimodal input through
existing `_convert_input_to_chat_message()` converter
## Reusable ChatMessageInput Component
- Extract chat input logic from agent-view into `ChatMessageInput` component
- Support file upload, drag & drop, paste handling, and attachments
- Add `useDragDrop` hook for parent-level drag handling with full-area
drop zones
- Refactor agent-view to use the new shared component
## Other Improvements
- Add `isStreaming` prop to executor nodes for animation control
- Clean up unused imports and state variables in agent-view
- Add tests for multimodal workflow input handling
Fixes workflow input not receiving images when using AgentExecutor nodes.
* add self loop edge, fix#2470
* fix test
* Add sample to show handoff as agent with HITL
* Update uv.lock with latest pkg versions. Fix lint error.
* Upgrade grpcio to 1.76.0
* Handle grpcio versions
* Case insensitive compare for declarative
* docs: Update Python orchestration documentation
Remove outdated 'coming soon' statements for GroupChat, Sequential,
and Concurrent orchestrations in core package README and transparency FAQ.
Add links to existing samples in python/samples/getting_started/workflows/orchestration/.
Note: python/README.md was already updated in PR #1914 (2499262f).
Fixes documentation inconsistency found in Issue #1899.
* Address review feedback: make TRANSPARENCY_FAQ language-neutral
Remove Python-specific sample links from TRANSPARENCY_FAQ.md as it should
pertain to all MAF languages (Python and .NET), not strictly Python.
The python/packages/core/README.md retains the specific sample links as
that is Python-specific documentation.
* Update Learn documentation link in README
---------
Co-authored-by: kishikawa-hayato <84244732+HerBest-max@users.noreply.github.com>
Co-authored-by: Victor Dibia <chuvidi2003@gmail.com>
* Standardize orchestration outputs as list of chatmessage. Add chat options to group chat prompt manager
* refactor group chat
* Improve group chat manager
* README Update
* Cleanup
* Add comment
* More cleanup
* Standardize termination condition for group chat
* Improvements on termination logic
* Fix tests
* Fix new line
* PR feedback
* Update ChatKit based on OpenAI type change
* Raise error if response format is not expected type
* Only one starting executor required. Add tests.
* Add magentic start executor test