1
00:00:00,000 --> 00:00:04,204
This prototype changes the case view into an Agent workspace.

2
00:00:04,204 --> 00:00:09,248
The main conversation stays clear, while delegated sub tasks do the work.

3
00:00:10,300 --> 00:00:13,604
First, ask which servers the agent can reach.

4
00:00:13,604 --> 00:00:18,561
The main thread acknowledges the request and delegates verification to a worker.

5
00:00:19,600 --> 00:00:24,070
Agent is working remains visible while the worker checks access.

6
00:00:24,070 --> 00:00:28,093
Commands and tool output never appear as conversation messages.

7
00:00:29,100 --> 00:00:32,786
When verification finishes, the main agent summarizes the result.

8
00:00:32,786 --> 00:00:38,520
These example results are simulated, and are not a fresh check of the servers.

9
00:00:39,600 --> 00:00:42,992
Hover over the agent response to reveal Logs.

10
00:00:42,992 --> 00:00:47,231
Keyboard focus and a touch menu provide the same access.

11
00:00:47,231 --> 00:00:49,775
Hover does not fetch execution details.

12
00:00:50,800 --> 00:00:54,286
Click Logs to open the sub task drawer.

13
00:00:54,286 --> 00:00:57,337
It shows task names, status, and timing.

14
00:00:57,337 --> 00:01:00,388
Select a worker to inspect its execution.

15
00:01:01,400 --> 00:01:06,958
Opening a worker starts an authorized request through Agents Hub to Robodev Agents.

16
00:01:06,958 --> 00:01:12,088
This loading state represents the proposed fetch, not a live backend connection.

17
00:01:13,100 --> 00:01:19,792
The drawer shows commands, tool results, and timestamps fetched from Robodev's canonical history.

18
00:01:19,792 --> 00:01:24,940
Hub keeps references and status, rather than another stored transcript.

19
00:01:26,000 --> 00:01:28,901
Closing the drawer stops its detail stream.

20
00:01:28,901 --> 00:01:35,118
The conversation and final answer remain available, without keeping raw worker logs in the chat.

21
00:01:36,200 --> 00:01:39,919
Next, ask why the latest deployment returns errors.

22
00:01:39,919 --> 00:01:45,498
The main agent starts separate workers for application logs and deployment health.

23
00:01:46,500 --> 00:01:49,273
Both workers appear in one task tree.

24
00:01:49,273 --> 00:01:54,026
The activity indicator stays on until the work and final summary finish.

25
00:01:54,026 --> 00:01:56,402
Their tool calls remain in details.

26
00:01:57,500 --> 00:02:02,409
Select the log worker to inspect its evidence from Robodev.

27
00:02:02,409 --> 00:02:07,808
This demonstration uses fixture events, including a simulated database connection timeout.

28
00:02:08,900 --> 00:02:13,202
The main agent combines the results into a concise update.

29
00:02:13,202 --> 00:02:20,086
It reports the suspected cause and suggests a next step, without making an unrequested production change.

30
00:02:21,100 --> 00:02:27,257
For a task that needs a missing credential, show a secure secret request in the main thread.

31
00:02:27,257 --> 00:02:30,516
The person enters the secret into a dedicated form.

32
00:02:31,600 --> 00:02:34,217
The task shows Waiting for a secret.

33
00:02:34,217 --> 00:02:38,702
The secret value goes to the vault, never to chat or logs.

34
00:02:38,702 --> 00:02:41,693
The main agent only receives the request status.

35
00:02:42,700 --> 00:02:46,910
Once the vault confirms receipt, the worker resumes with scoped access.

36
00:02:46,910 --> 00:02:52,651
Agent is working returns, and the main thread reports the result when it is ready.

37
00:02:53,700 --> 00:02:58,303
Agents Hub presents messages, questions, forms, and task status.

38
00:02:58,303 --> 00:03:05,974
Robodev runs the orchestrator and workers, and remains the source of truth for execution details.

39
00:03:07,000 --> 00:03:12,402
This is an animated interface prototype with simulated conversations and fetches.

40
00:03:12,402 --> 00:03:18,296
It illustrates the architecture proposal; the production application has not been changed.
