Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
codex/ag-ui-interrupts-implementation
3d6fb9b7 feat(interrupts)!: remove client-tool-execution from the public interrupt API Client tools resolve through their `.client()` implementation (auto-executed) or `addToolResult` — never as a bound interrupt. The `client-tool-execution` kind was redundant public surface: `resolveInterrupt(output)` and `addToolResult` were two doors to the same resolution, and it invited users to hand-wire client-tool execution that already happens automatically. The internal architecture is unchanged — the server still emits the client-tool-execution interrupt as the browser handoff, the client processor still auto-executes `.client()` tools off it, persistence still stores its binding. Only the public exposure is removed. - Remove `ClientToolExecutionInterrupt` from the `ChatInterrupt` union + exports - Filter client-tool-execution items out of the published `interrupts` / `pendingInterrupts` snapshot while keeping them in the internal batch so `resolveClientToolOutput` (addToolResult) and auto-execution still work - Exclude client-tool items from the `resolveInterrupts(cb)` completeness check and the boolean-bulk path (they resolve out-of-band; `maybeSubmit` still gates real submission on them) - Update ai-client + framework type tests and the e2e to assert the client tool auto-executes and stays out of the public interrupts array
by Alem Tuzlak
Failed
codex/ag-ui-interrupts-implementation
3d6fb9b7 Merge 31111a5dc70520e9037a330c3f3ea1b251ec3eb5 into 004180ca82837242cde4bdae52d8a31408f71e62
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
aedf2ded docs: stop presenting client-tool execution as a resolvable interrupt Client tools return results through their `.client()` implementation (which runs automatically) or `addToolResult` — not by resolving a client-tool-execution interrupt by hand. That manual path was redundant with the tool-result path and misrepresented how client tools work. - Delete docs/interrupts/client-tool-execution.md and its nav entry - Overview: list only tool-approval and generic as kinds you resolve; note client tools run automatically and approval is a separate axis - client-tools.md: drop the manual `execution.resolveInterrupt(...)` snippet; keep approval resolution + addToolResult as the manual escape hatch
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
aedf2ded Merge 647ae241e05546913c26c38968a234fa7e88bc08 into 004180ca82837242cde4bdae52d8a31408f71e62
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
f6a07dd1 docs(interrupts): render examples by looping interrupts, not find+narrow Replace the `interrupts.find(...)` + whole-component `return null` pattern in the tool-approval, generic, and client-tool-execution examples with a `interrupts.map()` that narrows on `kind` and renders per-kind UI. This handles multiple pending items of a kind and matches the mixed-queue pattern on the Multiple Interrupts page. Generic items get a per-item child component for their editor state.
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
f6a07dd1 Merge 18823d43971767827955f2036d92c2caf66f6755 into 004180ca82837242cde4bdae52d8a31408f71e62
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
52673e68 docs: clarify interrupt kinds are pauses, not tool categories The Overview "three kinds" table read as if a tool is either tool-approval or client-tool-execution. Add a note plus a tool→interrupt matrix showing the axes are independent: a client tool with needsApproval produces a tool-approval interrupt first, then a client-tool-execution interrupt once approved.
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
52673e68 Merge d3bf2e43c1028a35a2536fab70812ee09e317f9c into 004180ca82837242cde4bdae52d8a31408f71e62
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
88244391 docs: split interrupts into its own section Interrupts is a large feature; move it out of "Chat & Streaming" into a dedicated top-level Interrupts section and rewrite the content to be succinct and example-first with real, rendered React components. - New docs/interrupts/ pages: overview, tool-approval, multiple, generic, client-tool-execution, persistence, migration - Remove the monolithic docs/chat/interrupts.md and docs/migration/interrupts.md - Add the Interrupts nav section and drop the old entries in docs/config.json - Repoint inbound cross-links (chat, tools, persistence, architecture, and the generated toolDefinition reference) to the new paths Examples now show handling a single interrupt, mapping/batching multiple interrupts, and validating a generic responseSchema in the UI directly, instead of abstract helper functions.
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
88244391 Merge 75a53eb95cc6ab884c975c228a939f504fa25190 into 004180ca82837242cde4bdae52d8a31408f71e62
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
f01f3e41 fix: complete interrupt resume workflows
by Alem Tuzlak
Failed
codex/ag-ui-interrupts-implementation
f01f3e41 Merge 78d993cd24de26d88db6007242102c5ba9730e6c into 004180ca82837242cde4bdae52d8a31408f71e62
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
ada9b8a3 feat: add interrupt testing labs
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
ada9b8a3 Merge 0a09c7f314ede82c8b057b8bb604c1ad1edd5ac8 into 004180ca82837242cde4bdae52d8a31408f71e62
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
98eb45de Merge e5bc7d1751e267c121674b39f4d1165c84697df7 into 004180ca82837242cde4bdae52d8a31408f71e62
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
98eb45de fix: support interrupts without persistence
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
fb4356b7 test: allow slow persistence integration setup
by Alem Tuzlak
Succeeded
codex/ag-ui-interrupts-implementation
fb4356b7 Merge b77272883ae9885e9dfc1b5d719bb2c6aaf4377c into 659464a88b9e24f3a299d394a5e8b5da5e3e421a
by Alem Tuzlak