Support

FAQ

Use this page when you need a fast answer, then move into the deeper feature guide when the answer affects real execution or a product decision.

Guide summary

Use this page to understand the surface before you act inside it.

Practical answers to the most common questions about execution, BYOK, trust, reuse, and support.

Guide type

Support

This guide reflects the current product workflow and surface ownership.

Sections

5

Summary first, then steps, mistakes, and recovery notes.

Related guides

4

Written against the current product structure and core execution workflow.

Best use

Fast orientation

FAQ should help you decide which deeper guide to open next.

Common theme

Execution, trust, and ownership

Most questions come back to those three ideas.

Related action

Open the deeper guide next

If the answer affects real work, use the full feature page instead of stopping here.

Guide section

Core questions

Is opheli.ai a chatbot?

No. It includes conversational entry points, but the product itself is an AI Execution OS built around Missions, Tasks, Runs, Artifacts, and proof-of-work.

What is an AI Execution OS?

It is an operating environment for turning objectives into structured AI work with roles, review, execution tracking, and deliverables.

Do I need my own API key?

Not to explore the product. Mock Mode lets you validate the workflow without live provider cost.

Can I use Mock Mode?

Yes. Mock Mode is the safe no-cost path for learning the workflow.

Who pays provider/API costs?

Your connected provider account does when you use BYOK.

Are opheli.ai cost numbers exact?

They are estimates unless explicitly marked Verified by Provider.

Who determines my Provider charges?

Your connected Provider determines final charges, including free-tier limits, credits, taxes, discounts, and invoices.

Can opheli.ai prevent all provider charges?

opheli.ai provides budget guards and limits where available, but external Provider billing is controlled by the Provider.

How are API keys handled?

They are encrypted at rest, kept server-side, and not shown again after save.

What are Operators?

Specialized AI roles such as coordinator, researcher, analyst, reviewer, writer, or coder.

What is the difference between Mission, Task, Run, and Artifact?

Mission is the objective, Task is the work unit, Run is the execution record, and Artifact is the finished deliverable.

What is Context Vault?

The source-material layer for notes and supported uploads that can be attached to missions or tasks.

Guide section

Trust and guidance questions

What is Mission Replay?

The proof-of-work timeline showing how a run unfolded.

What is Mission Copilot?

The conversational command layer for explaining work and proposing product actions.

What is Mission Orb?

The persistent next-best-action and attention layer across authenticated product surfaces.

Can opheli.ai make mistakes?

Yes. AI output can be incomplete, risky, or wrong. Review still matters.

Should I review AI outputs?

Yes, especially for important business, legal, financial, operational, or technical decisions.

Guide section

Reuse and ownership questions

What are Blueprints?

Reusable execution patterns that prefill Mission Builder.

Can users publish Blueprints?

Users can create private reusable patterns, but Official Blueprints are curated and published only by opheli.ai.

What is Mission DNA?

A way to extract private reusable patterns from successful runs.

Guide section

Failure and support questions

What happens if a Run fails?

Inspect run detail and Mission Replay, then continue, retry, or report the run based on the actual failure posture.

Can I contact Support?

Yes. Use Contact Support or contextual report actions such as Report this Run.

What does support receive?

Safe context such as page and related-object references, not provider keys or hidden prompts.

Guide section

Where to go next

What it is

A route selector for deeper guidance.

When to use it

When a short answer is not enough for a real decision.

Where to find it

Open the linked guides from this page’s related articles.

What happens next

You move into the deeper workflow, feature, or troubleshooting guide.

Common mistake

Using FAQ as the only product documentation for complex setup or run issues.

Related action

Open the workflow guide or the exact feature page that matches the question.