Programmatic Control
Drive agent runs directly from code, with no chat UI required.
What is this?
Programmatic control is what you reach for when you want to drive an agent run from code rather than from a chat composer: a button, a form, a cron job, a keyboard shortcut, a graph callback. CopilotKit exposes three primitives that cover every triggering pattern:
agent.addMessage(...): append a message to the conversation without running the agent. Pair withcopilotkit.runAgent({ agent })when you want the appended message to kick off a turn.copilotkit.runAgent({ agent }): the same entry point<CopilotChat />calls internally. Orchestrates frontend tools, follow-up runs, and the subscriber lifecycle.agent.subscribe(subscriber): low-level AG-UI event subscription (onCustomEvent,onRunStartedEvent,onRunFinalized,onRunFailed, …). Pairs withcopilotkit.runAgent({ agent, resume })for standard AG-UI interrupts, orcopilotkit.runAgent({ agent, forwardedProps: { command: { resume, interruptEvent } } })for theon_interruptcustom events that the LangGraph adapter emits, to drive interrupt resolution from arbitrary UI.
When should I use this?
Use programmatic control when you want to:
- Trigger agent runs from buttons, forms, or other UI elements
- Execute specific tools directly from UI interactions (without an LLM turn)
- Build agent features without a chat window (to build your own chat UI, see Headless UI)
- Access agent state and results programmatically
- Create fully custom agent-driven workflows
Sending a message from code
Install the Antigravity AG-UI adapter
pip install ag-ui-antigravity google-antigravityWire the agent once — chat and code share it
copilotkit.runAgent, agent.subscribe and agent.addMessage drive runs
against the same AG-UI endpoint your chat UI posts to, so there is no
second backend to set up: build the AntigravityAgent the way any chat
demo does and every entry point sees the same model, tools and session.
def api_key() -> str | None:
"""The Gemini API key.
``GEMINI_API_KEY`` is the only name the Antigravity SDK reads. The showcase
fleet exports ``GOOGLE_API_KEY`` for its Gemini integrations, so accept
that too rather than fail on the first model call.
"""
return os.environ.get("GEMINI_API_KEY") or os.environ.get("GOOGLE_API_KEY")
def gemini_base_url() -> str | None:
"""The Gemini-compatible server to call instead of Google's API.
Showcase compose sets ``GOOGLE_GEMINI_BASE_URL=http://aimock:4010``, the
same variable the google-adk integration reads.
"""
return os.environ.get("GOOGLE_GEMINI_BASE_URL", "").rstrip("/") or None
def aimock_headers() -> dict[str, str]:
"""Headers for a model call: the package's fixture context plus the
current request's mock and diagnostic headers.
``X-AIMock-Context`` is fixed: it selects this package's fixtures whatever
the request says. The rest comes from the inbound request (captured by
``HeaderForwardingHTTPMiddleware``) and is forwarded only when present, so
ordinary demo traffic is never forced into strict mode.
"""
forwarded = {
k: v
for k, v in get_forwarded_headers().items()
if k.startswith(_FORWARDED_PREFIXES)
}
return {**forwarded, "x-aimock-context": SLUG}
def endpoint() -> GeminiAPIEndpoint | None:
"""Where every model call goes: aimock under compose, Google's API otherwise.
Passed to the adapter as a callable, so it runs each time a session is
built, inside that conversation's first request. The harness makes the
model calls itself, so headers can only reach them on the endpoint: the
request's ``X-AIMock-Strict`` and ``x-test-id``/``x-diag-*`` ride along
from here (PNI-576). They are fixed per conversation, because the SDK
sets a conversation's model configuration when it starts.
"""
base_url = gemini_base_url()
if base_url is None:
return None
return GeminiAPIEndpoint(
base_url=base_url,
api_key=api_key(),
http_headers=aimock_headers(),
)
def chat_only_capabilities() -> CapabilitiesConfig:
"""Only ``finish`` stays enabled.
``search_web`` returns an empty summary without Google credentials and the
model retries it forever; ``ask_question`` would park on an interrupt the
CopilotKit demos never answer. ``finish`` is how the harness ends a turn.
"""
return CapabilitiesConfig(
enabled_tools=[BuiltinTools.FINISH], enable_subagents=False
)
_DIRS_READY = False
def _ensure_dirs() -> None:
"""Creates the workspace / save_dir once, on first agent construction.
Deliberately NOT done at import time: the defaults live under ``/data``,
which only exists inside the container image, so an import-time
``os.makedirs`` blows up on a developer machine (read-only ``/`` on macOS)
and takes every ``import agent_server`` — including the package's pytest
suite — down with it.
"""
global _DIRS_READY
if _DIRS_READY:
return
os.makedirs(WORKSPACE, exist_ok=True)
os.makedirs(SAVE_DIR, exist_ok=True)
_DIRS_READY = True
_POOL = None
def shared_pool():
"""One HarnessPool for the whole server: one Go process, not one per agent."""
global _POOL
if _POOL is None:
from ag_ui_antigravity.harness_pool import HarnessPool
_POOL = HarnessPool()
return _POOL
def build(**kwargs):
"""Creates an AntigravityAgent with the package defaults applied."""
from ag_ui_antigravity import AntigravityAgent
_ensure_dirs()
defaults = dict(
model=MODEL,
api_key=api_key(),
endpoint=endpoint,
workspaces=[WORKSPACE],
save_dir=SAVE_DIR,
harness_pool=shared_pool(),
capabilities=chat_only_capabilities(),
session_timeout_seconds=SESSION_TIMEOUT_SECONDS,
max_sessions=MAX_SESSIONS,
max_tool_calls_per_turn=MAX_TOOL_CALLS_PER_TURN,
)
defaults.update(kwargs)
return AntigravityAgent(**defaults)
Sessions are keyed by thread_id inside the agent, so a headless run that
reuses a thread continues that conversation, and a fresh thread_id
starts a new one.
Headless interrupts come from server tools
The headless interrupt-resolver pattern — read the interrupt off the agent,
answer it with a resume — works when a Python server tool pauses with the
adapter's experimental_interrupt() (see the human-in-the-loop setup). The harness's
own ask_question built-in, which would also park on an interrupt, is
disabled in this showcase. For asking the user from code without a backend
tool, use the frontend-tool Promise pattern: register the tool with
useFrontendTool and an async handler, and resolve its promise when your
own UI has the answer.
The canonical pattern is to append a user message with
agent.addMessage, then call copilotkit.runAgent({ agent }). Use
copilotkit.stopAgent({ agent }) to cancel an in-flight run.
"use client";
import { useAgent, useCopilotKit } from "@copilotkit/react-core/v2";
export function AgentTrigger({ agentId }: { agentId: string }) {
const { agent } = useAgent({ agentId });
const { copilotkit } = useCopilotKit();
const run = async () => {
if (agent.isRunning) return;
agent.addMessage({
id: crypto.randomUUID(),
role: "user",
content: "Summarize the latest sales data",
});
try {
await copilotkit.runAgent({ agent });
} catch (error) {
console.error("CopilotKit runAgent failed:", error);
}
};
return (
<>
<button onClick={run} disabled={agent.isRunning}>
Run agent
</button>
<button
onClick={() => copilotkit.stopAgent({ agent })}
disabled={!agent.isRunning}
>
Stop
</button>
</>
);
}Click Run agent. The agent's reply arrives in agent.messages. To see it, render the last message, for example agent.messages.at(-1)?.content.
copilotkit.runAgent() vs agent.runAgent()
Both methods trigger the agent, but they operate at different levels:
copilotkit.runAgent({ agent }): the recommended default. Orchestrates the full lifecycle: executes frontend tools, handles follow-up runs, and routes errors through the subscriber system.agent.runAgent(options): low-level method on the agent instance. Sends the request to the runtime but does not execute frontend tools or chain follow-ups. Reach for this only when you need direct control.
Subscribing to agent events
agent.subscribe(subscriber) returns { unsubscribe }. The subscriber
object accepts every AG-UI lifecycle callback: onCustomEvent,
onRunStartedEvent, onRunFinalized, onRunFailed, and the streaming
deltas. Use it to drive custom progress UI, forward events to
analytics, or catch framework pause/resume events and resolve them with
a payload (the pattern below).
Resolving a frontend tool call from a button
For promise-based integrations there is no native interrupt primitive.
The demo uses useFrontendTool with a Promise-based handler instead.
The handler stages its resolve callback and pending payload via React
state, the app surface renders the picker outside the chat, and the
user's pick resolves the Promise that the agent's tool call is awaiting.
The user sees the same flow. Only the mechanism is different. The agent
does not know that a button grid answers in place of a chat picker:
Not available for Google Antigravity yet
interrupt-headless demo, and Google Antigravity doesn't have it yet.The handler stores pending in state and a resolver in a ref. Any UI
can call the resolver. The demo itself renders a simple button grid, but the
same pattern would power a modal, a toast, a sidebar form, or a voice
UI. To pause inside the chat instead, see Human-in-the-Loop.
How is this guide?