Om-EIntelligence Dashboard

layout lab: hero 1 · you are herehero 2hero 3hero 4hero 5hero 6

Your browser, transformed into an agentic AI knowledge base.

An agent that reads your pages, PDFs and transcripts, organises the mess, and answers with sources — all on your machine.

what did that PDF say about pricing?
  • Q3 Pricing Deck.pdfClient · Acme
  • Pricing call — transcriptSales KB
  • market pricing researchResearch

macOS · Chrome extension · local-first

· explore ·

World first

The world's first AI context engineering tool.

Every AI answer is only as good as the context it was given. Om-E ships that discipline as a product: the context window is yours to run — what the model sees, what it ignores, and what you pay — on every single turn.

01

Attach vs load

Retrieval-only when the KB should answer, full text when the model must read every word.

02

Scoped per chat

Each chat sees the knowledge you point it at — nothing else bleeds in.

03

Cheaper by design

Tokens are the bill. Sending less, better-chosen context is the discount.

04

Sharper answers

Less noise in, less noise out — the model reasons over what matters, not everything.

Context engineering

You decide what the model sees.

Behind every answer is a build step: Om-E assembles the exact window the model will read — your question, the thread so far, and only the knowledge you've dialled in.

Attach a KB and each turn carries just the retrieved slices that match the question. Load a topic and its full text rides along. Skip, and the model answers cold. Nothing bleeds between chats — and every token in the window is one you chose to spend.

An ice control console with three sluice gates — one open with documents streaming through, one filtering a thin trickle, one closed with a dim queue waiting
A vertical violet conduit running top to bottom: chaotic page fragments raining into an ice funnel, ordered into a tower of circular ice database discs, narrowed through a segmented ice aperture, arriving as a green-sealed stack of verified pages
gate

Feed it anything

PDFs, images, transcripts, spreadsheets. Drop them in — they come out searchable.

Every page you capture and file you add is read, structured and vectored — automatically, as it lands. No tagging, no filing, no format wrangling: if you can open it, you can ask it questions.

gate

Local RAG

Your files become vectors. On your machine. For good.

Drop in a PDF, a page, a transcript. Om-E chunks it, turns it into vectors and stores them in a local index — that's local RAG: retrieval that runs on your machine, not in someone's cloud. Ask a question and the right pieces come back, with receipts. Nothing uploads, nothing expires.

All use cases →
The frozen-glass database, fully indexed
indexed · searchablelocal RAG · on your machine
  • 01
    Standup · 12:04
  • 02
    Standup · 12:04
  • 03
    Standup · 18:22
  • 04
    Standup · 19:40

chats

Where the work happens.

A chat works like any AI conversation — until you connect it. Attach a topic and local retrieval feeds the model exactly the passages that matter; load it and the full text sits in the window for whole-document work. Pull in several and the chat becomes the place where sources meet: joined, compared, cited.

the full story →

one chat, two sources

attachvendor-a KB · retrieval on

loadvendor-b brief · full context

ask“compare their security posture”

both cited · verification report saved

topics

The unit of reuse.

A topic is born from almost anything: a file you import, a page you capture, a transcript you pull, a note you write. Import an architecture document and the text is vectored — and so are the images inside it, searchable through the same store. Diagrams answer questions now.

the full story →

one document import

importsolutions-architecture.pdf

vectortext chunked · 18 images embedded

ask“the network diagram?”

diagram surfaced · document cited

knowledge bases

It understands meaning, not just keywords.

A knowledge base is an organised library of topics — a project, a client, a research area, a family wiki. Om-E chunks and vectors what's inside into an index that lives on your disk, so it searches by meaning: ask about “my daughter's creative interests” and it finds the note that says she likes drawing.

the full story →

found by meaning

topic“Amber started school, likes drawing”

ask“my daughter’s creative interests?”

matchmeaning, not keywords

grounded answer · topic cited

multi-session

Nothing waits for anything.

Each chat is its own session: its own context, its own knowledge scope, its own running work. Fire a deep research run in one chat, draft in a second, triage in a third — they run side by side, and every thread keeps its own trail.

the full story →

three chats, one afternoon

chat 1deep research · vendor sweep · running

chat 2drafting the client memo

chat 3triaging inbox questions

all three land · nothing waited

gate

Run it

It answers under your rules.

Every turn, you choose what the model reads, which persona reads it, and what the run may spend — and when your KB can't answer, the agent goes out and finds out.

A frosted ice globe floating in darkness, pulling in glowing documents along violet threads
gate

Proof

Every answer arrives with its evidence.

Om-E answers from your captured sources and shows exactly where each claim came from: the document, the section, the capture date. Compliance reviews, policy work, audits — anywhere “trust me” isn’t good enough, hand the answer over and the receipts go with it.

  1. 01Policy requires 12-month retention — cut from 24 in the new draft.Policy v2 · §6 · PDF · captured 09 Jul✓ verified
  2. 02Backups are configured for 18 months — six over the new limit.Ops runbook · backup schedule · captured 02 Jul✗ conflict
  3. 03Breach notice window is now 30 days; the runbook still says 60.Policy v2 · §4.2 · PDF · captured 09 Jul✗ conflict

Captured sources don’t rot — the page you cited in March is still the page you cited, even after the live site changes.

Verified documents sealed inside a block of frosted ice

Stop losing knowledge in tabs.

Ask the page. Save the answer. Build your knowledge base.