Agno

Select the server interface

Agno AgentOS provides an AGUI interface around an agent or team. Its current documented route is POST /agui (optionally prefixed). Use the maintained AgentOS interface rather than older AGUIApp examples. Configure the model, session storage, agent/team identity and authentication server-side. Follow the Agno integration for server installation and its current Python dependencies. These are maintained server integrations, not new Ghost runtime packages. The verified Ghost boundary is the AG-UI frontend path; the examples do not claim a live Python deployment was tested.

First React integration

Complete the AG-UI React recipe, passing your endpoint URL and a real application/native thread ID. Install @ag-ui/client@1.0.3 plus view dependencies. That client owns event reduction; Ghost projects its messages and sends through its native run command.

The working client, send/stop controls and errors are canonical in that recipe. Keep the native client available for shared state, interrupts and richer resume payloads. Validate state before using it in application UI; tool execution, persistence and authorization remain server/caller-owned.

Customize for the job

A research workflow can render tasks or artifacts beside the transcript rather than forcing every state change into a message. Use native shared-state notifications and MessageParts.renderers for validated custom parts. Do not infer a boolean tool approval from every human-input pause.

Troubleshooting

An HTTP success with no answer often means the endpoint speaks a different protocol or protocol version. Confirm the server route, credentials and event content type before changing Ghost. For unavailable native operations, retain the native API or implement a narrow application adapter; do not report unsupported behavior as success. See Agno's documentation and stability for each side of the boundary.