Product · planned first private release

Everything planned for the first private release

Five families of capability, 22 in all. Each shows how far along it is. None are available to the public yet.

Planned capabilities: 22in 5 areas
Maturing in private development: 7
In development for the first private release: 13
Conditional on platform support or authorization: 2

These capabilities are planned for OptiML’s first full private release. They describe intended product scope while that release is completed—not features already available to the public.

01 · 5 capabilities

Intelligence & persistent context

Conversation, memory, people, decisions, and evidence that carry from one piece of work to the next.

Conversational AINatural-language task interaction—ask for outcomes without learning a separate command language.MaturingMaturing. Maturing in private development—not a claim of public availability
Why it matters
Work should start from what you mean, not which menu you remember.
Example
“Prepare me for tomorrow’s design review.”
Maturing in private development—not a claim of public availability
Persistent structured contextDurable context across commitments, relationships, preferences, and ongoing work.In developmentIn development. In development for the first private release
Why it matters
Continuity removes the need to re-explain your world every session.
Example
Return later and continue from prior commitments and notes.
In development for the first private release
People & relationship intelligenceResolve people and related context across authorized evidence.MaturingMaturing. Maturing in private development—not a claim of public availability
Why it matters
Most work is interpersonal—context about people matters.
Example
“What do I owe A. Rivera before Thursday?”
Maturing in private development—not a claim of public availability
Decision historyChronological reconstruction of decisions and related evidence over time.In developmentIn development. In development for the first private release
Why it matters
Past choices should remain inspectable when work resumes.
Example
Reconstruct why a follow-up was promised and when.
In development for the first private release
Source visibility & freshnessSee which sources were used, what is available, and how current the evidence is.MaturingMaturing. Maturing in private development—not a claim of public availability
Why it matters
Trust requires inspectable grounding—not opaque answers.
Example
Open the evidence panel and check coverage before acting.
Maturing in private development—not a claim of public availability

02 · 4 capabilities

Execution & workflows

Controlled workflows, supported business systems, bounded computer use, and sourced research.

Reusable controlled workflowsRepeat multi-step work with explicit control and confirmation points.In developmentIn development. In development for the first private release
Why it matters
Recurring work should be reliable without becoming unsupervised.
Example
Run a prep-and-follow-up workflow after you authorize it.
In development for the first private release
Business-system interactionInteract with work through supported integrations you authorize.In developmentIn development. In development for the first private release
Why it matters
An operating layer must reach the systems where work already lives.
Example
Use connected systems as evidence and action surfaces.
In development for the first private release
Bounded browser & computer useUse the browser and computer within supported, bounded controls.ConditionalConditional. Conditional on platform support or authorization
Why it matters
Some work still requires operating interfaces—not only APIs.
Example
Complete a supported sequence after you authorize the steps.
Conditional on platform support or authorization
Public web researchResearch with supported sourcing and verification.In developmentIn development. In development for the first private release
Why it matters
External information should arrive with sources you can check.
Example
Gather background with links you can inspect.
In development for the first private release

03 · 3 capabilities

Files & document intelligence

Search your files, understand documents and attachments, and generate new documents from what you already have.

Local file search & document Q&ASearch authorized local files and ask questions against documents.In developmentIn development. In development for the first private release
Why it matters
Much of your knowledge already lives on your machine.
Example
“Where did we define the launch criteria?”
In development for the first private release
Advanced document understandingUnderstand supported attachments and OCR where available.In developmentIn development. In development for the first private release
Why it matters
Work often arrives as PDFs, scans, and mixed formats.
Example
Extract key points from a supported attachment.
In development for the first private release
File & document generationCreate useful documents from available information.In developmentIn development. In development for the first private release
Why it matters
Starting from context is faster than starting blank.
Example
Generate a one-pager from meeting notes and commitments.
In development for the first private release

04 · 8 capabilities

Work management & proactivity

Meetings, mail, calendars, reminders, and scheduled briefings—plus opportunities spotted from your own history.

Email intelligenceReview conversations and extract useful signal from authorized mail context.MaturingMaturing. Maturing in private development—not a claim of public availability
Why it matters
Mail is where commitments and open loops accumulate.
Example
Summarize a thread and list open questions.
Maturing in private development—not a claim of public availability
Reply preparation & verified draftsPrepare replies for review and create Gmail drafts after explicit approval.MaturingMaturing. Maturing in private development—not a claim of public availability
Why it matters
Outbound communication should stay under your control.
Example
Confirm to create a Gmail draft—never silent send.
Maturing in private development—not a claim of public availability
Meeting preparationAssemble prep from authorized meeting, people, and communications context.MaturingMaturing. Maturing in private development—not a claim of public availability
Why it matters
Preparation should not require hunting across five apps.
Example
Briefing with attendees, open items, and talking points.
Maturing in private development—not a claim of public availability
Calendar & scheduling intelligenceAgendas and scheduling reasoning across authorized calendar context.MaturingMaturing. Maturing in private development—not a claim of public availability
Why it matters
Time pressure is easier when the week is coherent.
Example
“What does my week look like, and what’s dense?”
Maturing in private development—not a claim of public availability
Availability & open timesCheck availability and propose open times from authorized schedules.In developmentIn development. In development for the first private release
Why it matters
Scheduling should reuse calendar truth you already maintain.
Example
Propose two open windows next week for a follow-up.
In development for the first private release
Work attention & follow-upsReminders, commitments, and attention on what likely needs you next.In developmentIn development. In development for the first private release
Why it matters
Important loops should not depend on memory alone.
Example
Surface overdue commitments and candidate follow-ups.
In development for the first private release
Proactive opportunity detectionSurface opportunities grounded in authorized behavioral evidence.In developmentIn development. In development for the first private release
Why it matters
Useful suggestions should come from real patterns—not generic prompts.
Example
Flag a dense week against an approaching commitment.
In development for the first private release
Scheduled preparation & briefingsRelevant briefings prepared on a schedule when useful.In developmentIn development. In development for the first private release
Why it matters
Preparation can arrive before pressure peaks.
Example
A morning briefing for the day’s key meetings.
In development for the first private release

05 · 2 capabilities

Connected platform experience

Voice, optional local-model paths where supported, and desktop operation on macOS and Windows.

Voice & optional local modelsVoice interaction and optional local-model capabilities where supported.ConditionalConditional. Conditional on platform support or authorization
Why it matters
Work happens away from the keyboard—and privacy preferences vary.
Example
Speak a request, or prefer a local-model path when available.
Conditional on platform support or authorization
macOS & Windows operationInstall and operate OptiML on macOS and Windows desktops.In developmentIn development. In development for the first private release
Why it matters
A work assistant should live where serious work happens.
Example
Run OptiML as a desktop application on your machine.
In development for the first private release

How a request becomes a result

Requests in all five areas are designed to follow the same path, from intent to a verified outcome.

01
Intent
You describe the outcome in plain language.
02
Context
Relevant evidence from the sources you’ve authorized.
03
Capabilities
The supported tools and skills suited to the request.
04
Reasoning
Answers and plans built from available evidence.
05
Verified outcome
A clear result, with confirmation when action matters.

Private early access. Capability descriptions reflect planned scope, not a public product.

Read the vision Request free early access

The full capability catalog

How a request becomes a result

Intent

Context

Capabilities

Reasoning

Verified outcome