451a864096
Evidence carried the first 200 characters of every message the agent read. Remove it: messages now report identity and provenance only. Message content is caller-supplied and unbounded -- up to MAX_MESSAGE_SIZE, 25k characters -- and a single answer can touch a few hundred messages across its search, grep and date-range tools. Carrying even a slice of each invites callers to read messages in bulk out of evidence rather than fetching the ones they want, which is the opposite of what this is for: evidence is an audit and analytics surface, not a read API and not something to sit in a hot path. Conclusions keep their text, which is the asymmetry worth stating. A conclusion is written by the deriver, is short, and is the thing being audited; a message is raw input that already has endpoints of its own. 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.