Expand description
Durable harness state that sits above gemini-live-runtime and below a
concrete host application.
gemini-live-runtime already owns hot-session orchestration, tool-call
request fanout, and short-lived in-process conversation continuity. This
crate is the next layer up:
- tasks are durable filesystem records under one harness root
- notifications are durable queue items, not ephemeral callbacks
- memory is stored on disk and may be inspected directly by other agents
- shared host-tool execution contracts live next to harness policy
- harness-owned wrappers may keep blocking host tools within an inline latency budget and spill eligible calls into durable background tasks
HarnessControlleris the preferred host-facing boundary for combining tool execution and passive notification delivery
The default root is ~/.gemini-live/harness, but callers may supply any
alternative path for testing or custom deployments.
Structs§
- Harness
- Top-level file-backed durable harness.
- Harness
Controller - Host-facing harness boundary above the runtime layer.
- Harness
Notification - Persisted notification record stored under
notifications/. - Harness
Paths - File layout configuration for the durable harness.
- Harness
Profile Store - Generic typed host profile store backed by the harness filesystem.
- Harness
Runtime Bridge - Non-cloneable runtime bridge that owns tool-completion plumbing for one host runtime event loop.
- Harness
Task - Primary persisted task record.
- Harness
Tool Budget - Harness-owned inline budget for host tool calls.
- Harness
Tool Completion - Result of one host-side tool call spawned by the harness controller.
- Harness
Tool Forward Failure - Failure while forwarding one tool completion back into the runtime.
- Harness
Tool Forward Outcome - Summary of one tool completion after it has been forwarded back into the runtime.
- Harness
Tool Registry - Normalized view built from one host-fed provider.
- Harness
Tool Runtime - Composite harness executor that wraps host-local tools with harness-owned inline-budget policy.
- Memory
Record - Persisted harness memory entry addressed by
scopeandkey. - Memory
Write - Request to upsert a durable memory record.
- NewNotification
- Request to enqueue a durable notification.
- NewRunning
Task - Request to persist a task that is already running inside the current runtime instance.
- Noop
Tool Source - Empty downstream tool source used by hosts that do not expose local tools.
- Passive
Notification Delivery - One queued passive notification that should be injected into the model.
- Passive
Notification Pump - Reusable passive notification pump backed by durable harness state.
- Registered
Tool - One normalized function entry inside the harness registry.
- Task
Detail - Rich task projection returned to hosts and tools.
- Task
Event - Append-only event stream for task lifecycle changes.
- Task
Result - Persisted terminal result for a successful task.
- Task
Runtime Instance - Process/runtime instance metadata for a task that is already executing.
- Tool
Capability - Per-function capability declared by the host and consumed by the harness.
- Tool
Descriptor - Metadata about a host-defined tool exposed to users or debuggers.
- Tool
Specification - One model-callable function declared by a host-fed provider.
Enums§
- Harness
Error - Failures while reading, writing, or interpreting on-disk harness state.
- Harness
Tool Completion Disposition - High-level result class for one host-side tool call.
- Notification
Kind - Notification categories used by the harness.
- Notification
Status - Durable delivery state for a queued harness notification.
- Task
Event Kind - Event payload variants stored in
events.jsonl. - Task
Status - High-level durable status for one persisted harness task.
- Tool
Execution Error - Failures while resolving or executing a host-defined tool call.
- Tool
Kind - High-level tool categories for host-side presentation.
Traits§
- Tool
Executor - Host-fed blocking execution surface for locally executable tools.
- Tool
Provider - Host-fed metadata surface describing which tools exist.
Functions§
- format_
passive_ notification_ prompt - Render a durable harness notification into a model-facing prompt.