Your knowledge deserves a home, and a librarian who keeps it current. Intentface OS is an agent-native brain for everything your team knows.
One knowledge base
Just‑in‑time context for agents and humans
Built for people
Read moreCompose yourself or with agents. Brand templates present your knowledge the way people prefer to read it, not as raw markdown.
what's our discount policy again?
15% on annual plans, from pricing.md
Slackbot in your Slack
Ask from any channel and get cited answers, and stamp trust right inside the conversation, where it costs nothing.
App in your pocket
Capture a note, index a link, or find a quick answer when you're on the go.
Built for agents
Read moreBrowsing and reading tools built for machines, so agents find what they need fast. Scoped access keeps each one to what you allow.
What did we agree about events yesterday?
Let me search your knowledge base for the past meeting notes.
searchMCP for AI clients
Claude Desktop, Claude Code, or any MCP client: the assistant orients itself and reads the same workspace you do.
Scoped API
A documented REST API with an OpenAPI spec and scoped keys, so you can build your own agents, integrations, or front end.
Filesystem
Real files, structured data, living views
No proprietary blobs. A workspace is a folder tree you control, and it survives export, import, and any database.
Folders as access boundaries
A folder decides which people and agents can read it. Every file inside inherits the answer.
Every folder has a table of contents
A generated toc.md lives in every folder, a plain markdown file like the rest. It is the first thing an agent reads.
PDFs and images indexed
Contracts, decks and whiteboard photos are read into text and searchable the moment they land.
Pricing
Discounts
Markdown
Documents are real markdown files: prose, guides, meeting notes. Portable, diff-able, fully versioned, written in a rich editor that keeps the file clean.
SELECT stage, sum(value) FROM dealsDatabase
Build tables for the structured data that never sat well in prose: deals, hours, inventory. To you it is a table; to an agent it is a database it queries with SQL.
View
A sandboxed React page over one or more of your databases: a dashboard, a report, or a small interactive app. Generated in one gesture, styled with the workspace's own design tokens.
Agent-first search tools
Multiple ways to find information
Agents get four routes to the same knowledge: a folder's table of contents and authored facts to orient, a concept index in your team's vocabulary, a graph of who and what each file touches, and search that resolves terms before it ranks results. Each route is deterministic and explainable, so an answer can always say where it came from.
- Atlas & Co/Notes, deals, and the 2026 contract
- Beacon Ltd/Proposal in progress
- kickoff-checklist.mdWhat to set up before day one
Billing
- Invoices go out on the 1st, net 30terms.md
- Discounts above 15% need a founder's sign-offpricing.md
Renewals
- Atlas & Co renews in March 2027contract-2026.pdf
- Beacon Ltd is on a pilot until Q1proposal.md
Table of contents & authored facts
Every folder carries a toc.md: a generated table of contents with a line per file, plus facts that people and agents write by hand. It is the first thing an agent reads. When an agent finds a conflict, or a change that outdates a fact, a human validates it before anything is rewritten.
The concept index
As files are saved, Intentface OS builds a back-of-the-book index of what they are about: canonical names in your team's vocabulary, aliases, scope notes, and every place a concept lives. Human edits are law; the rest maintains itself.
The context graph
Underneath the files sits a graph of people, files, and concepts: every @mention, every backlink, every see-also. Related ideas stay one hop apart, so an agent follows edges instead of guessing.
- Product/onboarding-revamp-spec.md
- Meetings/2026-08-14-steering.md
- Ops/rollout.db
Search built for agents
Every team has its own dictionary: codenames, ticket prefixes, words that mean something specific here. Search consults it first, expands a query to every alias, and only then runs full-text. Agents get the same route through concept_resolve, so results are explainable and never a vector guess.
Authoring flows
Every change has a name on it
Documents that are reference truth shouldn't change just because someone has edit access, and nothing is ever silently overwritten, by people or by agents.
Anyone edits
Agents read it as is
Live mode
The file is what agents read, as it is right now. Every edit by a person or an agent lands immediately. Right for notes, logs and working documents.
Anyone drafts
Owner publishes
Agents read the published copy
Published documents
People and agents contribute to a draft, but agents only read the published version. Nothing changes for them until an owner publishes. Right for pricing, policies and anything an agent will quote as truth.
Full history, portable
Documents keep restorable versions; tables keep a row-level changelog with named save points; a workspace-wide audit trail logs which tool ran, on what, by whom. All of it survives export and re-import.
Scoped API keys
Hand a narrow slice of the workspace to an external agent or integration: folder-pinned, expiring, shown once and stored only as a hash.
Platform agents
Native agents that keep the place in order
Intentface OS ships with platform agents, native agents that run on a schedule inside your workspace, and the means to build your own.
Reading /changes since yesterday
5 files changed
Good morning, Mike
Nothing new yet.
Run on a schedule, or on change
Build agents that run nightly, hourly, or the moment a file lands. Scheduled runs and durable execution come with the platform; you write what the agent does.
Scoped to their own folders
Give an agent a folder-pinned key and it works inside that slice of the workspace: reading what it may read, writing where it may write, and nothing else.
Context prefixed, not fetched
Set what an agent sees at the start of every run: a folder's table of contents, its facts, a live query. The context arrives with the prompt, so runs stay short and cheap.
The workspace is shared memory
Agents read and write the same files people do. What one agent learns tonight another reads tomorrow, and a person can open it, correct it, or delete it.
Use cases
Company brain, agent brain, personal brain
The same librarian, pointed at three different problems. Each one is just a workspace: scoped, indexed, and reachable by people and agents alike.
Company brain
The core use case: your organisation's knowledge base: shared vocabulary, trusted sources, every team and every agent reading from the same room.