Kluff connects your tools and keeps the relationships between people, decisions, and work. Capture that context once. Every agent can use it.
From capability to everyday work
The company brain combines workspace context, project memory, search, and connected tools. It helps an agent start with the relevant company knowledge instead of asking the team to explain the same background again.
“Prepare a pilot brief using the decisions we already made.”
Locate the relevant project discussion and memory.
Bring together the decision, its background, and the current task.
Use the relevant context to draft the next piece of work.
Most AI tools see one chat. Kluff keeps the company around it.
Keeps
Decisions, facts, and workflows from topics, projects, and Jams — available to the people and agents who should see them.
Connects
CRM, finance, docs, and support, plus any MCP server. One connection serves the workspace, with that tool’s permissions intact.
Follows
The same context shows up in threads, Slack, flows, and agents. Switch models and the memory stays in Kluff.
Context with depth
A private chatbot sees the message in front of it. The company brain also sees who decided what, which project it belongs to, and which tools are allowed to act.
People and agents work from the same organizational knowledge—no more siloed chats or disconnected workflows.
Capture decisions, workflows, discoveries, and expertise automatically so nothing valuable gets lost.
Reuse successful work instead of starting from scratch. When someone finds a better approach, the entire team benefits.
The organization becomes smarter with every interaction. Your company's intelligence compounds over time.
What it holds
Threads, memory, search, and tools. An agent checks them before it asks the team to explain the company again.
Threads
Topics, DMs, and Jams keep the conversation. When it gets long, Kluff compresses the earlier part so the thread still knows how it started.
“What did we tell Harbor about the renewal?” starts from the thread, not a blank chat.
Every front door
People pick the surface. The company brain does not stay inside one chat window.
Ask in any thread. The agent starts from project memory and the tools that project can use.
Learn moreThe same workspace context is available where the team already talks, without a second setup.
Learn moreAdd a server once. Projects opt in, and every call stays inside the scopes you set.
Learn moreSchedules and pipelines run on the same memory, so automation does not start from zero.
Learn moreWith and without
| Job | A private chatbot | Company brain |
|---|---|---|
| Answer a question | A new chat with no company history. | Project memory and workspace search already in the thread. |
| Hand work to someone else | A recap meeting so they can start. | The decision, the reason, and the next step are already there. |
| Connect a tool | Every person pastes their own token. | One connection. Teammates request access. |
| Change models | Context stays inside one vendor’s chat. | Memory stays in Kluff. The model is replaceable. |
Team stories
“Property details, client preferences and viewing notes used to sit in separate conversations. Kluff keeps them together, so any agent on our team can pick up a client relationship without asking them to start again.”
How it fills
The company brain is not a second wiki to maintain. It fills from threads, projects, and the tools you connect.
Topics, DMs, projects, and Jams are where the context is created.
Decisions, facts, and routines from that work become memory the project can use again.
Permissions follow the tool. Risky actions can ask before they run.
People and agents begin from what the team already learned.
FAQ
It is the shared context Kluff keeps for a workspace: conversation history, project memory, workspace search, connected tools, and the files a project holds. Agents use it instead of starting from a blank chat.
No. Those systems stay the source. Kluff connects to them and keeps the decisions your team makes on top of them, so an agent can use both.
Project memory stays with that project. Direct messages are searchable only by the people in them. Tool access follows the permissions on the connection.
No. Threads keep their history, and agents look up facts the project already established. You still choose which tools to connect and which actions need approval.
The memory stays in Kluff. Instant, Balanced, and Thinking are ways to run a request. They do not own the company’s context.
Connect your tools, ask your first question in a project, and watch memory, spend, and visibility stay in one place—not scattered across personal chats.
$15 / user · Unlimited AI
@kluff build a launch dashboard from HubSpot and the Q4 budget sheet. Refresh it every morning.

Done. Signups come from HubSpot, spend from the Q4 budget sheet. It refreshes at 7:00 AM.
v2 adds the channel split you asked for.

Can we flag any channel over $40 per trial?

Added. Paid social is flagged.
It sends from your Gmail, as you, with the draft attached. Nothing else leaves the project.
Ana Chen confirmed net 45 at 9:18 AM. Your rule: every customer email waits for you.