Honcho, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Honcho account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Artificial Intelligence
- Connects with a key
- 16 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Honcho is
Honcho provides memory, context, and theory-of-mind infrastructure for building stateful AI agents.
You paste in a key from your own Honcho account. It is kept encrypted, and you can withdraw it from inside Honcho whenever you like.
One message in, the work done in Honcho.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Honcho. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Honcho account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Honcho
These are the ready-made tools your AI employee already has in Honcho. It is not limited to them, but it never has to be taught these.
- Chat With PeerRun usage-bearing agentic search and reasoning over a peer's learned representation to answer a question. Higher reasoning levels generally cost more and take longer. Returns one n
- Create ConclusionsStore a batch of 1-100 explicit conclusions about peers, optionally tied to sessions.
- Create MessagesAdd a batch of 1-100 attributed messages to a Honcho session. Message-level reasoning settings can trigger usage-bearing processing.
- Delete SessionPermanently delete one known session and its session-scoped data. Honcho marks the session inactive immediately and completes deletion asynchronously.
- Get MessageReturn one message by its exact ID within a session.
- Get or Create PeerReturn a peer by ID within a workspace, creating it with the supplied metadata and configuration when absent. Existing peers are returned unchanged.
- Get or Create SessionReturn a session by ID, or create it with initial peers, metadata, and configuration when absent. Creation may create missing peers and start usage-bearing processing when reasonin
- Get or Create WorkspaceReturn a workspace by ID, or create it with metadata and configuration when absent. Enabling reasoning features during creation may start usage-bearing background processing.
- Get Peer RepresentationReturn a curated subset of conclusions representing a peer. Supplying searchquery performs semantic retrieval and may consume paid search capacity; omit it for the existing default
- List ConclusionsReturn one page of stored conclusions in a workspace; use Search Conclusions for semantic retrieval.
- List MessagesReturn one page of messages in a session; use Get Message for exact-ID retrieval.
- List PeersReturn one page of peers in a workspace.
- List SessionsReturn one page of sessions in a workspace.
- List WorkspacesReturn one page of Honcho workspaces visible to the connected admin key.
- Search ConclusionsSemantically search stored conclusions in a workspace. This operation may consume paid search or embedding capacity; use List Conclusions to browse stored conclusions without seman
- Search MessagesSemantically search messages at workspace, peer, or session scope. WARNING: this operation may consume paid search or embedding capacity; use list or get message tools for exact or
You stay the boss of your Honcho account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Honcho account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Honcho is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Honcho and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Honcho
- Can an AI employee really work inside Honcho?
- Yes. It signs in to your own Honcho account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Honcho?
- No. Nothing moves and nothing is replaced. Your records stay in Honcho, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Honcho account?
- You paste in a key from your own Honcho account. It is kept encrypted, and you can withdraw it from inside Honcho whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Honcho?
- It has 16 ready-made tools in Honcho today, among them Chat With Peer, Create Conclusions and Create Messages. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Honcho and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Honcho and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Honcho?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Honcho is written down with what it did and when.