You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/ai-sre/sessions.mdx
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -226,10 +226,11 @@ Beyond subagents, the agent can push time-consuming work into the background. Ta
226
226
| shell | The `bash` tool with `run_in_background`| A long one-shot command (build, batch job, data pull); only its completion needs reporting |
227
227
| monitor | The `monitor` tool | A standing watcher task: watches a condition until it hits or reaches its deadline, and the script's output flows back to the agent as event batches; a one-shot delayed action (e.g. "check again in half an hour") is done with a monitor plus `sleep`|
228
228
229
-
A unified **Tasks** panel on the right side of the session tracks every task of the session, grouped into **Needs you / Running / Finished**. There are two entry points:
229
+
A unified **Tasks** panel on the right side of the session tracks every task of the session, grouped into **Needs you / Running / Finished**. There are three entry points:
230
230
231
231
-**The tasks button in the chat header**: carries a count badge for "needs you + running" tasks, capped at `9+`; the badge is red when any task needs you (awaiting authorization / awaiting input), and blue when tasks are only running.
232
232
-**The generation status row while a turn is running**: shows the live task count (e.g. "3 tasks · 1 agent needs you"); clicking it opens the same task panel.
233
+
-**The tool row that started a monitor / background bash**: the tool row in the conversation that started a `monitor` or a background command (`bash` with `run_in_background`) — when it is the only tool in its group, that group's header — is itself that task's handle in the transcript: its trailing external-link icon marks it clickable, the tooltip reads **Open task detail**, and clicking it opens that task's detail panel directly. Such rows no longer expand into raw Input/Output (a background bash row used to show only the command, with no status or output). In a read-only shared session the detail opens in read-only mode as well.
233
234
234
235
Task details differ by kind: clicking an **agent** task opens the child session's execution transcript (see above); clicking a **shell / monitor** task opens its own event-timeline detail, which includes the status (a running task also shows how many seconds ago its last liveness probe landed — probing happens roughly every 30 seconds), run duration, event count, output bytes, the monitor's deadline (standing tasks with no deadline show "Persistent"), the exit code, the full command, and the event timeline in order. **The stop button lives in the detail header** — **Stop task** for shell / monitor tasks and **Stop Subagent** for subagents — and interrupts only that task, without affecting the main session.
235
236
@@ -238,7 +239,7 @@ How this surfaces in the conversation stream:
238
239
- A tool line that starts a background command reads **Started background command**; when a turn mixes foreground and background commands, the collapsed tool group counts each category separately (e.g. `Ran 1 command, started 1 background command`).
239
240
- Each time a monitor's condition hits, a 🔭 system line is inlined into the conversation: the first line shows the monitor's description plus a first-line summary of that output batch, and clicking it expands the full batch in place.
240
241
- When a task ends, a terminal line appears with the end state and a result summary, plus the exit code and a note when the task envelope carries them.
241
-
- The `monitor` tool line itself does not expand into input / output — the bookkeeping it returns (task ID, output file, deadline, and so on) is presented more completely in the task panel's detail.
242
+
- The `monitor` tool line itself does not expand into input / output — clicking it opens the corresponding task's detail panel, where the bookkeeping it returns (task ID, output file, deadline, and so on) is presented more completely.
242
243
243
244
Two status indicators related to background tasks:
<Updatelabel="2026-09-07"description="👥 SSO sync configuration: sync roles and teams by identity provider claims">
8
+
9
+
### SSO sync configuration: role and team sync
10
+
11
+
The SSO settings page for SAML2.0 / OIDC / CAS gains a **Sync Configuration** section that syncs a member's roles and teams at login based on fields returned by the identity provider (IdP):
12
+
13
+
-**Sync roles / Sync teams toggles**: enable role or team sync independently; at login, the member's current roles and teams are overwritten with the matching result
14
+
-**Role field / Team field**: the claim names carrying the role and team names returned by the IdP (e.g. `roles` / `teams`); the value may be a string or a string array, matched by name **exactly** (case-sensitive)
15
+
-**Default roles / Default teams**: when no returned name matches any role or team, the configured defaults are assigned at login; if nothing matches and no defaults are configured, they are cleared
16
+
-**Protocol differences**: LDAP is unchanged — it still maps Group DN to roles/teams; this sync configuration applies only to SAML2.0 / OIDC / CAS
17
+
18
+
See [Role and Team Sync](/en/on-call/integration/sso/role-team-sync).
19
+
20
+
</Update>
21
+
22
+
<Updatelabel="2026-09-07"description="🧰 Monit datasource diagnostics and new datasource types">
23
+
24
+
### Monit datasource diagnostics and new datasource types
25
+
26
+
Monit datasources gain **datasource diagnostics**: run structured read-only named-tool inspections against a configured datasource:
27
+
28
+
-**Datasource diagnostic tool**: invokes exactly one deterministic tool per datasource ID (e.g. `mysql.lock_contention`, `postgres.activity`, `redis_node.slowlog`, `kafka.consumer_lag`, `elasticsearch.cat`, `prometheus.metric_trends`, `loki.log_patterns`, `victorialogs.log_patterns`); there is no tool catalog, and the datasource must have `enabled=true` (`alerting_enabled=false` does not block diagnostics)
29
+
-**Version requirement**: all routable online Edge sessions in the selected cluster must support the **v0.71.0** baseline protocol, otherwise errors such as `edge_upgrade_required` / `mixed_edge_versions` / `no_active_edge` / `tool_not_supported` are returned
30
+
-**Legacy tools removed**: `mysql.query` / `postgres.query` are gone — use the query API for free-form SQL
31
+
-**Five new diagnostic-only datasource types**: Redis (Node / Sentinel), MongoDB (Mongod / Mongos), and Kafka — for diagnostics only, they never evaluate alerts; address formats are a single `host:port` (bracket IPv6) or 1–32 unique comma-separated Kafka bootstrap addresses
32
+
-**Switch semantics split**: `alerting_enabled` (whether the datasource may evaluate alerts; always false for diagnostic-only types, and disabling it is rejected with a conflict while enabled rules reference the datasource) is now independent of `enabled` (business execution, on by default at creation)
33
+
34
+
See [Data Sources](/en/monitors/data-sources/data-sources) and [Monitoring Targets](/en/monitors/targets/overview).
35
+
36
+
</Update>
37
+
7
38
<Updatelabel="2026-09-04"description="🔭 AI SRE background task panel, RUM WeChat Mini Program remote config, incident list filter bar">
0 commit comments