7b3d331846
Add an opt-in `include_evidence` to both chat endpoints. The response then carries the conclusions and messages the agent read while answering, plus the tools it called. Evidence is collated from what the agent accessed rather than reported by the model. That over-reports -- a conclusion appears because the agent saw it, not as proof the answer used it -- but it is deterministic, costs no model tokens, and behaves the same at every reasoning level. Asking the model to cite its sources fails quietly instead: weaker models produce incomplete or invented citations, and a sparse citation list is indistinguishable from a sparse answer. The prefetch already makes the point, feeding explicit conclusions into the prompt without their IDs, so the model could not cite them if asked. An accumulator is threaded from the router through the agent into ToolContext, and read handlers hand it the rows they already loaded. Nothing is re-queried when the response is built, so evidence inherits the scoping of the reads that produced it and cannot become a way around a session allowlist. Three details worth knowing: - Prefetched conclusions never pass through the tool executor, so they are captured via a new `documents_out` sink on `search_memory`. On a query that answers without a tool call they are the whole of what was read. - Conclusions dedupe by ID. `Representation`'s own deduplication keys on content and timestamp and ignores IDs, which would collapse distinct conclusions that happen to read alike. - Conclusion timestamps are re-stamped UTC. `Representation` strips tzinfo so observations render compactly into prompts, which would otherwise put naive timestamps in the API beside timezone-aware message ones. The two chat routes had byte-identical nested SSE formatters; they now share one helper, so the terminal event carries evidence on both. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| changelog | ||
| images | ||
| logo | ||
| snippets | ||
| v1 | ||
| v2 | ||
| v3 | ||
| README.md | ||
| bun.lock | ||
| docs.json | ||
| favicon.svg | ||
| package.json | ||
| posthog-consent.js | ||
README.md
Honcho Docs
These docs are built using Next.js via mintlify.
Setting Up Honcho's Docs Locally
- Clone the repository:
git clone git@github.com:plastic-labs/honcho.git
- Navigate into the
docsfolder:
cd honcho/docs/
The docs folder contains the markdown files that make up the documentation. The majority of the files are in the pages directory. Some notable files in this folder include:
- Verify that you have Node.js and npm installed in your system. You can check by running:
node --version
npm --version
-
If not installed, download Node.js and npm from the respective official websites.
-
Once you have Node.js and npm running, proceed to install
pnpm- another package manager that helps to manage project dependencies:
npm install -g pnpm
- Install the project dependencies using pnpm:
pnpm i
- After the successful installation of the project dependencies, start the local server:
pnpm dev
Now, you should be able to view the docs on your local environment by visiting http://localhost:3000. You can explore the different markdown files and make changes as you see fit.