DoneOS app → Connect → Execute → Activity
This walkthrough crosses the boundary the protocol-only demo cannot: DoneOS explains the connection in its own settings, accepts a real MCP write, shows the resulting task in Queue, and attributes the event to the connected agent in Activity.
Live-walked against the committed DoneOS Flutter app and local Firebase emulators. The disposable credential was never shown and disappears when the emulator session ends.
Opened Connect and inspected the AI Agents panel.
DoneOS explains what the MCP credential does before it asks for one: the connected agent can work the shared Queue, and every action is attributed in Activity. The empty state shows the supported clients and makes it clear that a key does not start an agent by itself.
Connected with the generated local credential, then created and independently read back a task through the official MCP SDK.
After the call, the credential appears as Walkthrough Agent with its usage state inside the product. The one-time token never appears in the capture.
Opened Execute, then Queue after the MCP write completed.
The exact high-priority task created through MCP appears in DoneOS beside the normal app controls. It is not a terminal transcript or a mocked result; this is the Flutter product reading the same emulator-backed state.
Opened Activity and found the creation event.
DoneOS records the write as an execution event attributed to Walkthrough Agent. That closes the user-facing loop from connection settings, to MCP action, to visible task, to an auditable history.
