Files
Mark b4041622b0 feat(examples): LangGraph interrupt HITL probe for channels
Adds a minimal, runnable test rig for the channels HITL path that nothing in
the repo previously exercised: `onInterrupt` + `thread.resume()`, driven by a
real LangGraph graph that suspends in its checkpointer.

Channels has two unrelated HITL models, and they suspend in different places:

  thread.awaitChoice()   a channel-side tool handler blocks; the agent run
                         stays open; the waiter is an in-memory Map
  onInterrupt/resume     the AGENT's graph suspends; the run ENDS; the click
                         starts a new run carrying the resume value

Only the first had coverage. `examples/integrations/langgraph-python` has zero
`interrupt()` calls, and `examples/slack/e2e/restart-recovery.ts` — written for
this exact path — no longer compiles (it imports `@copilotkit/slack` plus
`appComponents`/`appHitl`, none of which still exist).

What's here:

- `agent-py/` — a LangGraph agent whose `create_thing` tool calls `interrupt()`
  and writes nothing, so the interrupt fires deterministically with no
  Linear/Notion credentials. Served over AG-UI, so the channel dials it
  directly and `runtime.ts` is not involved.
- `agent-py/probe.py` — drives the agent alone (no channel, no Slack).
- `e2e/route-b-interrupt.ts` — drives agent + channel with a `FakeAdapter`
  standing in for the platform, so a failure is unambiguously channels' fault.
  Asserts the resume leaves in the legacy `forwardedProps.command.resume` shape.
- `app/route-b.ts` — the Slack-facing probe, plus a boot-time preflight that
  rejects an unreachable/mangled `AGENT_URL` with a specific diagnosis instead
  of a bare `fetch failed` on the first message.

Two wire facts worth recording, since both fail silently:

- `on_interrupt` is not a label you choose. It's the AG-UI custom event name
  LangGraph's adapter emits, and adapters default `interruptEventNames` to
  exactly that. Rename either side and the graph stays suspended forever.
- the interrupt payload crosses as a JSON *string*. All four real adapters
  parse it before the handler runs; `FakeAdapter` does not, so handlers that
  assume an object work in Slack and break headless. Both handlers here
  normalize defensively.

Nothing in `packages/` changes; this is examples-only.
2026-08-03 08:53:30 +00:00
..