Run codeagent's chat engine inside a host Shiny app

Wires the same server side that codeagent_app() uses – streaming with per-turn compaction, stop / ESC interrupt, /skill commands, hooks, token budget and per-turn session saving; the approval and question bar (AskUserQuestion); the generative UI canvas; and Data Shield – to a client the host built for this Shiny session. Pair it with codeagent_chat_ui() and codeagent_head_assets(), and with codeagent_canvas_ui() when canvas is given.

Usage

codeagent_server(
  input,
  output,
  session,
  client,
  tools = list(),
  tool_meta = list(),
  canvas = NULL
)

Arguments

input, output, session

The Shiny server arguments.

client

A codeagent_client() built for this session.

tools

Host tools (a list of ellmer::tool() definitions). Each must have a capability in tool_meta. They are registered after the built-in tools, with codeagent's result normalization, behind the permission gate and Data Shield.

tool_meta

Named list or character vector: host tool name -> capability ("read", "write", "exec" or "net").

canvas

NULL (no canvas) or canvas_options() to enable the generative UI canvas; place codeagent_canvas_ui() in the page. With a tools= selection on the client, include "genui" in it.

Value

Invisibly, a list with state (the session reactiveValues), stream_task (the ExtendedTask), chat and settings.

Details

Build the client per session with codeagent_client(..., register_tools = FALSE); tools are registered once the UI has flushed, after the Shiny approval / question callbacks exist, so the interactive tools are created in their UI-gated form. Select built-in tools with the client's tools=.

See also

codeagent_chat_ui(), codeagent_canvas_ui(), codeagent_app()