Directories
¶
| Path | Synopsis |
|---|---|
|
Command basic is the runnable end-to-end example for resolute-harness-go: one agent definition with per-instance setup, a SQLite store, a logging Observer, a timing Interceptor, and one real tool, served over HTTP.
|
Command basic is the runnable end-to-end example for resolute-harness-go: one agent definition with per-instance setup, a SQLite store, a logging Observer, a timing Interceptor, and one real tool, served over HTTP. |
|
Command chat is the browser example for resolute-harness-go: a single Go binary serving an embedded HTML chat page over the harness's own HTTP surface — no npm, no build step, no external assets.
|
Command chat is the browser example for resolute-harness-go: a single Go binary serving an embedded HTML chat page over the harness's own HTTP surface — no npm, no build step, no external assets. |
|
Command coder is the coding-assistant example for resolute-harness-go: one agent wired to the four built-in execution tools (read, write, edit, bash) from resolute-agent-core-go's tools package, rooted at a workspace directory, with a stdout observer that narrates tool activity — including a running bash command's partial output — as it happens.
|
Command coder is the coding-assistant example for resolute-harness-go: one agent wired to the four built-in execution tools (read, write, edit, bash) from resolute-agent-core-go's tools package, rooted at a workspace directory, with a stdout observer that narrates tool activity — including a running bash command's partial output — as it happens. |
|
Command github-bot is the channel example for resolute-harness-go: verified GitHub webhook ingress translated into signal dispatches, with delivery-id idempotency and one narrow application-owned tool that posts the agent's reply back to the issue.
|
Command github-bot is the channel example for resolute-harness-go: verified GitHub webhook ingress translated into signal dispatches, with delivery-id idempotency and one narrow application-owned tool that posts the agent's reply back to the issue. |
|
Command multitenant is the concurrency-model example for resolute-harness-go: one agent definition serving many tenants, where the instance id picks the tenant (per-instance system prompts via Initialize) and sessions inside an instance give independent, durably ordered conversations.
|
Command multitenant is the concurrency-model example for resolute-harness-go: one agent definition serving many tenants, where the instance id picks the tenant (per-instance system prompts via Initialize) and sessions inside an instance give independent, durably ordered conversations. |
|
Command scheduler is the time-driven example for resolute-harness-go: an in-process ticker fires scheduled signal dispatches into a durable conversation, and deterministic per-window dispatch ids make the schedule idempotent — a killed-and-restarted process re-fires the current window's dispatch and the store deduplicates it, so nothing runs twice.
|
Command scheduler is the time-driven example for resolute-harness-go: an in-process ticker fires scheduled signal dispatches into a durable conversation, and deterministic per-window dispatch ids make the schedule idempotent — a killed-and-restarted process re-fires the current window's dispatch and the store deduplicates it, so nothing runs twice. |
|
Command triage is the structured-results example for resolute-harness-go: a bug-triage endpoint where the dispatch carries a resultSchema, the harness validates the run's final answer against it, and the corrective retry loop is visible in the record stream.
|
Command triage is the structured-results example for resolute-harness-go: a bug-triage endpoint where the dispatch carries a resultSchema, the harness validates the run's final answer against it, and the corrective retry loop is visible in the record stream. |
Click to show internal directories.
Click to hide internal directories.