AI agent

Give your agent the whole business.

Your agent is already capable. What it’s missing is context. Oknola’s structure is context an agent can actually use: every file typed, tagged and organized, in plain files it already knows how to read, with only the tags you allow.

The problem

Your agent is smart. It just can't see.

Point the best model in the world at your business and it gets one chat window and whatever you paste into it. The real state of your operation, from clients and offers to money and commitments, is scattered across apps your agent can’t read, or lives in your head, which it can’t read either. Meanwhile your best thinking is scattering into the chats themselves: ideas lost across conversations you'll never scroll back through, the connections between them gone.

The bottleneck stopped being intelligence. It's context.

Why plain files

A folder is the universal interface.

Every serious agent reads and writes files natively: it’s the one interface they all share. No API keys, no integration project, no waiting for an official connector.

If your business is a folder of plain text, any agent can work on it today, and any agent released next year can too. That’s why Oknola keeps nothing in a database: the files are the source of truth, and the files are the interface.

The Business agent in the demo, on WhatsApp. Asked which design partner is stalling, it reads 3 files in Entities, checks the pilot invites in Projects and the meetings, then answers: Acme Corp, Pilot invite v2 went out on August 22, 19 days ago, no reply, and the last touch was the first interview on August 14. A follow-up is drafted and filed in Actions. — The Business agent in the demo: it reads the client files, the ledger and the meetings, answers, and files the follow-up. Ask it →

What the structure adds

Readable isn't the same as understood.

A folder of random notes is readable, not legible. Three things turn Oknola's folder into something an agent can genuinely operate on:

Every file follows OKF.

The open, vendor-neutral markdown standard Google introduced in 2026, designed precisely for handing an agent curated context. Typed, tagged, described: the agent knows what a file is before reading a word of it.

Organized by Indexed Brain.

Our architecture. Predictable structure at any scale, so an agent finds your finances, your clients, your commitments where the structure says they are. Navigation, not guesswork.

Oknola enforces both.

So the structure never rots. Stale structure is how you get a confidently wrong agent; enforcement is how you get one that stays right.

OKF

standardizes the file

Indexed Brain

organizes the files

Oknola

keeps both true while you work

If you’ve let an agent loose on a vault, you know the other failure: it “reorganizes” your files into rubble. Enforcement runs in both directions. What an agent writes has to conform to the schema too, typed, tagged and filed where it belongs, or it doesn’t land. And because everything is plain text, version control works: every change inspectable, every change reversible. An agent wrecks an unstructured vault. Structure is the seatbelt.

Bring your own agent

Works with the agent you already trust.

Claude, Codex, OpenClaw, Hermes: if it can read a folder, it can work on your business. On your desktop, point it at the structure and ask. On a server, run a 24/7 harness like OpenClaw or Hermes on a machine you control, working the same synced folder while you sleep. Your agent, your infrastructure, your files.

Run as many as you like: one for the business, one for your life, one per client. Each is a contact in your phone that knows only the files with the tags you gave it.

Desktop

Claude · Codex

Point it at the structure and ask.

Server, 24/7

OpenClaw · Hermes

A harness on a machine you control, on the same synced folder.

We don’t pick your agent. The structure is agnostic by design: compatibility isn’t a partnership we signed, it’s a property of plain files. No MCP server, no plugin, no connector to wait for.

The agent panel in the demo: a Business agent for every file tagged as business, a Personal agent, a Marketing agent for notes, ideas and resources, and an Acme Corp agent for one design partner, plus Add an agent. Below: an agent is a contact in your phone that knows the files with the tags you gave it, and nothing else, running on OpenClaw or Hermes on a machine you control. — The agent panel in the demo. Four scopes, four sets of tags.

The boundary

It sees what you point it at.

Business and personal share one structure, and tags are the permission model. An agent gets the tags you give it, nothing more, whatever folder a note sits in: your pipeline without your journal, your training log without your client files.

And the two-state doctrine always holds: agent off, your files never leave your device; agent on, you chose the scope.

The Business agent in the demo. It answers which design partner is stalling and files the follow-up. Then, asked how you slept this week, it refuses: journal pages are tagged Daily_Log, a Life tag, and this agent is not allowed Life files. Its scope shows business and shared tags allowed and life tags dashed out, and the switches show Business and Shared on, Life off. — The Business agent in the demo: it answers about clients, and refuses your journal, because Life is switched off. Try it in the demo →

Where this sits on the roadmap

True today. Bigger later.

Everything above about bringing your own agent is true of OKF plain files right now: it’s how the founder runs his own business today.

Further out sits the Oknola agent layer: full orchestration, an agent that holds your entire business context and works across every app. In order, not on dates; the layers underneath ship first.

See the Roadmap

Waitlist

Put an agent on your business.

The free app comes first, on macOS and Android. Early access opens in waves.