What Truffle does, and what it does not.

The loop: post, work, decide.

A channel keeps the same team, services, rules, and outputs ready for every new post. The post is the boundary for one piece of work; the thread is where it happens.

1. 01 — Post

   Name the job

   Start a campaign, case, candidate, incident, or launch as a top-level post in the right channel.

2. 02 — Work

   Keep every response in its thread

   Teammates and approved services add messages to that post's thread without spilling responses into another job.

3. 03 — Decide

   Approve with the record in view

   Owners make the final call in context. The thread preserves who decided, what changed, and what shipped.

Set the channel up once.

Choose the members, named roles, provider connections, partner services, workflow steps, message outputs, and approvals for that function.

• Post-first channels — the channel groups ongoing work by function, and each top-level post names a separate job.
• Thread boundaries — replies stay inside their post's thread, so one job cannot silently become part of another.
• Reusable roles — assign who drafts, reviews, approves, or receives the handoff without rebuilding the process for each post.
• Connected services — assign a provider connection, partner service, or your own service to each step with only the channel access it needs.
• Thread results — each step returns a message in the thread for the post that started the workflow.
• Access-aware search — search messages, threads, and files while channel membership continues to decide what each person can read.
• Scanned attachments — files are scanned before download and remain attached to the post or thread where the work happened.
• Explicit approvals — sensitive decisions can require a fresh passkey, and approval authority stays with the designated owner.

One connection, verified once.

A team owner selects a provider preset or an HTTPS endpoint your team controls, stores one key, and verifies the connection in Account.

Channel managers assign a named connection to each step without exposing credentials in posts.

A channel for the function, a thread for each job.

Truffle keeps ongoing work visible without turning every request into one continuous group conversation.

The claims register.

Each line is one shipped behaviour, quoted from the register that ships with the product. Nothing is listed here before the surface behind it exists.

• Agents are members of a channel, not a separate console.
• Agent work runs as a Run with a plan, a live transcript, a budget and a cancel button.
• A run shows you its plan before it does anything.
• You review what an agent changed one hunk at a time and accept or reject each.
• Approvals arrive in the channel and record their outcome in place.
• Every run reports what it spent, and daily limits can cap it.
• Agent tools reach the internet through a broker that substitutes credentials at the edge, so no secret enters the sandbox.
• A run takes instructions from the person who started it, never from the text it is reading.
• A pull request becomes a thread, with its checks and reviews posted into it.
• Routines run on a schedule or a trigger and tell their owner when they fail.
• Search ranks messages instead of matching them literally.
• Agents recall what the workspace has told them before, scoped to that workspace.
• Messages written offline are delivered in order after a reload or a crash.
• Channels stay smooth to scroll at tens of thousands of messages.
• Everything is reachable from the keyboard, through one palette and one shortcut map.
• Every route is checked for accessibility in light, dark and high-contrast themes.
• Workspace roles decide who can approve, invite and configure.
• Agents and their permissions are defined as files you can review in a pull request.
• Notifications tell a mention apart from an agent making progress.
• The download page states the signing and update status of each desktop release and provides its verification links.

Your team stays in control.

Channel membership limits who can read the work. Connected services use named roles. Sensitive approvals stay with the people assigned to decide.

• Channel accesspublic or membership-bound
• Post threadsseparate for every request
• Credentialskept out of posts
• Service rolesexplicitly scoped
• Sensitive decisionsowner-approved
• Sensitive actionsfresh passkey step-up

Start.

Run it locally with one command, install the desktop app, or create an account and sign in from the web.

Download · Pricing · Create account