Ortivo user guide
Reviewed and updated 28 October 2026. Start with the steps below, then use the contents to find a feature. Basic Help & Fix works without an AI connection; an optional AI explanation is a separate reviewed request.
Start here
Ortivo lets you ask AI services, compare their answers and work with documents in one workspace. Web and News search and basic Help do not require a personal AI-provider key.
- Sign in to Ortivo and open Chat.
- For an AI answer, open Connections and connect one provider. An API key is a private access code that lets Ortivo send requests to your provider account. Check that account’s API billing, credits and usage limits; an ordinary chat subscription does not automatically cover API use.
- Choose one connected provider and an available model. Ask a short question. Review costs and recipients before sending.
- For websites or news without an AI answer, use + → Web search. Choose Web or News and open the source links.
Connect your first provider · Understand usage costs · How your data is handled
Settings: connections, models and costs
Connect only the providers you intend to use. Provider API access, available credits and model permissions must be checked in each provider account.
- Open Settings and choose OpenAI, Claude, Gemini or OpenRouter. Open its official API-key guide below.
- Create a dedicated key in that provider’s dashboard. Review account access, API billing, model permissions and available spend controls. No local software installation is required.
- Paste the key only into the matching password field in Settings, review the storage consent and click Verify & connect. Never paste it in Help or Chat.
- Refresh available models, then choose a model you can access. A configured connection or model list does not guarantee a successful generation request.
- Start with a short text-only question to one provider when you choose to test. A test is a paid AI request unless the provider account specifically covers it.
- Disconnect removes the active saved key from Ortivo; revoke a compromised key separately in the provider dashboard.
Troubleshooting API connections
- 401 / invalid key: verify provider and account; create a replacement if revoked or exposed.
- 403 / permission: check project, workspace, region, API permissions and model access.
- 429: distinguish rate limiting from exhausted quota/credit or spend controls in the provider dashboard; wait or fix the specific cause before retrying.
- Unreadable/timeout: check provider status and usage before manual retry. Refreshing or retrying is not a refund mechanism.
OpenAI: obtain and connect an API key
No software installation is needed. Create the key on the official provider website, then connect it in Ortivo Settings. Never enter it into Help or Chat.
- Sign in to the OpenAI API platform and choose the intended organisation/project. ChatGPT billing is separate from API billing.
- Review API billing, available credits, project permissions and model access. Set practical spend controls or alerts; an alert is not necessarily a hard cap.
- Open API keys and create a dedicated secret key for Ortivo. Copy it securely when displayed; if lost, create a replacement.
- Return to Ortivo Settings. Paste the dedicated key into the OpenAI password field, review the consent and click Verify & connect.
- Refresh models and select a model available to your API account. When ready, send one short text-only question to this provider in Chat; provider charges may apply.
- If a key is exposed, revoke it on the provider’s API-key page, create a replacement and reconnect it in Ortivo. Disconnecting in Ortivo does not revoke it at the provider.
Troubleshooting OpenAI API keys
- Invalid key: check provider, project/workspace, expiry and whether it was revoked. Never send the key to support.
- Access denied: check account role, API restrictions, model permissions and regional availability.
- Quota/rate error: inspect API credit balance, spend controls and rate limits.
- Connection appears configured but generation fails: inspect the provider dashboard/status and selected model; no automatic paid retry is performed.
Anthropic Claude: obtain and connect an API key
No software installation is needed. Create the key on the official provider website, then connect it in Ortivo Settings. Never enter it into Help or Chat.
- Sign in to the Claude Console and choose the correct organisation/workspace. Review the API account’s own billing and access, including any account-specific credits.
- Open API keys. Create a dedicated key for your intended workspace and appropriate use; your account role controls which keys you can create.
- Check available API credits/billing, spend/rate limits and model access. Consumer plan names alone do not establish what API usage is covered.
- Return to Ortivo Settings. Paste the dedicated key into the Anthropic Claude password field, review the consent and click Verify & connect.
- Refresh models and select a model available to your API account. When ready, send one short text-only question to this provider in Chat; provider charges may apply.
- If a key is exposed, revoke it on the provider’s API-key page, create a replacement and reconnect it in Ortivo. Disconnecting in Ortivo does not revoke it at the provider.
Troubleshooting Claude API keys
- Invalid key: check provider, project/workspace, expiry and whether it was revoked. Never send the key to support.
- Access denied: check account role, API restrictions, model permissions and regional availability.
- Quota/rate error: inspect API credit balance, spend controls and rate limits.
- Connection appears configured but generation fails: inspect the provider dashboard/status and selected model; no automatic paid retry is performed.
Google Gemini: obtain and connect an API key
No software installation is needed. Create the key on the official provider website, then connect it in Ortivo Settings. Never enter it into Help or Chat.
- Sign in to Google AI Studio and open Get API key. Select or create the intended Google Cloud project following Google’s current key setup flow.
- Create a Gemini API key using the current AI Studio flow. Key type, API restrictions and project access affect whether it will work. Keep the key private.
- Review Gemini API billing, model availability, quota, region and free/paid tier conditions for that project. Do not assume a Google consumer subscription covers this API usage.
- Return to Ortivo Settings. Paste the dedicated key into the Google Gemini password field, review the consent and click Verify & connect.
- Refresh models and select a model available to your API account. When ready, send one short text-only question to this provider in Chat; provider charges may apply.
- If a key is exposed, revoke it on the provider’s API-key page, create a replacement and reconnect it in Ortivo. Disconnecting in Ortivo does not revoke it at the provider.
Troubleshooting Gemini API keys
- Invalid key: check provider, project/workspace, expiry and whether it was revoked. Never send the key to support.
- Access denied: check account role, API restrictions, model permissions and regional availability.
- Quota/rate error: inspect API credit balance, spend controls and rate limits.
- Connection appears configured but generation fails: inspect the provider dashboard/status and selected model; no automatic paid retry is performed.
OpenRouter: obtain and connect an API key
No software installation is needed. Create the key on the official provider website, then connect it in Ortivo Settings. Never enter it into Help or Chat.
- Sign in to OpenRouter and open Settings → API keys. Create a dedicated key for Ortivo.
- Review credits, model pricing and any per-key credit limit. A free model may still have access/rate constraints; do not assume every model is free.
- Check your provider privacy/routing settings. Ortivo’s current integration is text only and requests routing without data collection or endpoint retention, which can reduce available models.
- Return to Ortivo Settings. Paste the dedicated key into the OpenRouter password field, review the consent and click Verify & connect.
- Refresh models and select a model available to your API account. When ready, send one short text-only question to this provider in Chat; provider charges may apply.
- If a key is exposed, revoke it on the provider’s API-key page, create a replacement and reconnect it in Ortivo. Disconnecting in Ortivo does not revoke it at the provider.
Troubleshooting OpenRouter API keys
- Invalid key: check provider, project/workspace, expiry and whether it was revoked. Never send the key to support.
- Access denied: check account role, API restrictions, model permissions and regional availability.
- Quota/rate error: inspect API credit balance, spend controls and rate limits.
- Connection appears configured but generation fails: inspect the provider dashboard/status and selected model; no automatic paid retry is performed.
Chat: ask, compare and follow up
Use one AI for a focused answer, or compare independent answers from connected providers. Each selected provider may charge your API account.
- Open Chat and choose Single AI or Compare. Select connected providers and an available model for each.
- Write the outcome you want, relevant facts, constraints and preferred answer format. Check the recipient line before sending.
- Web off is selected for new chats. Choose Web on manually when needed, or explicitly select Auto. Review brief, memory and attachments before each request.
- Send once, wait for completion and read each provider’s result and usage separately. Ask a follow-up in the same conversation or start a new chat for a separate task.
- Use Review with AI Council to challenge successful answers. Save a useful decision in the notebook; export before leaving an unsaved session.
Troubleshooting AI chat and comparisons
- Send unavailable: connect a provider and choose a model in Settings.
- One provider failed: retain successful answers; check that provider’s billing, model access and status before a manual retry.
- Slow or unreadable response: wait for the active request to finish and check provider usage before retrying; a failed screen does not prove that no charge occurred.
Open Chat · Open Council · Open Settings
More detail and practical checks
Choosing a model
The dropdown is populated from models returned by your connected provider account. Recommended available models appear first, followed by the remaining models. An absent model is not automatically created or made accessible by Ortivo.
Choose a model appropriate to the task and cost you accept. A model appearing in the list does not establish that it supports every file format or every optional tool. Image, PDF and web-search support differ. Provider permissions, billing and availability can also affect requests.
When Web search is switched on, Ortivo retains a compatible selected model or picks the first supported model in each selected provider’s available dropdown. Providers with no compatible option are deselected with an explanation. Gemini is currently deselected because Ortivo has not enabled Gemini search. No additional provider is added automatically.
Turning Web search off retains the current model choices. If you manually choose an unsupported model while search is on, the request is blocked until you select a supported model or turn search off. Model recommendations and support can change in future plugin releases.
Loading indicators and waiting
During ordinary chat and search, the active answer card displays an animated indicator, a provider-specific message and elapsed seconds. After 20 seconds, the message says that Ortivo is still waiting for the provider. This is elapsed time, not an estimate of time remaining.
Selected providers run in parallel, each with its own loading display. Completed answers remain visible if another request fails. Loading wording does not claim that an AI is verifying a source or completing a particular internal step.
Keep the page open while waiting. Avoid repeated clicks, duplicate tabs or immediate resubmission after an error. Ortivo does not automatically retry failed requests. A browser timeout does not prove the provider stopped processing or did not bill the request. Check the provider usage dashboard before trying again. The interface has no guaranteed provider-side cancellation control.
AI-assisted web search in Chat
- Choose your connected provider or providers and type your question.
- Web off is the default. Ortivo does not automatically enable web search for new chats. Choose Web on manually when you want a search-enabled request. Auto remains an optional mode that uses local question cues without a separate AI classification request.
- Choose Web on to require a search-enabled request, or Web off to prevent web search. Starting a new chat restores Web off.
- Click Send. Ordinary Chat does not ask for another search confirmation. A visible loading indicator shows when a search-enabled request is running.
- Read the explanation and linked evidence together. Check the result’s search status and open the sources; search-enabled does not guarantee that the provider actually searched. If search fails, Ortivo shows a failure message.
Search uses supported OpenAI and Claude models available to your API account. Gemini web search is not enabled. Selecting OpenRouter makes every answer in that comparison text only. The composer says “Web: text only” and “Auto · text only”; remove OpenRouter to use Auto search. Web on with OpenRouter is blocked rather than silently downgraded.
Search requests cannot include attachments or an attached brief in this release. Search may share derived queries with search services; conversation context goes to each selected provider. Provider search and token charges apply, and one request can involve several searches. The usage estimate is not a billing guarantee or dollar cap.
Search evidence may be incomplete or stale. Distinguish retrieved page content from indexed snippets and check dates. Click outside the + tools or model menu to close it, or press Escape.
More detail and practical checks
Understand evidence and search labels
| Label | Meaning | What it does not establish |
|---|---|---|
| Page retrieved | Ortivo obtained accepted page text and supplied a limited excerpt to the AI. The URL and UTC retrieval timestamp are shown. | That every part of the page was included, all claims are true, links work or the whole site was audited. |
| Could not access page · search results only | Direct reading did not return usable page text. Any search evidence must be assessed separately. | That the website is offline, empty, parked or unrelated to the topic. The AI may also have performed no search. |
| Web search completed · accuracy not verified | The provider reported a completed search tool operation. | That the sources are fresh, sufficient, relevant or correctly interpreted. |
| Provider did not report a completed web search | No completed provider search was reported for that answer. | That page reading failed. A retrieved page may already have supplied the needed information. |
| Web search incomplete or error | A search operation was incomplete or reported a tool problem. | That the answer is verified or that repeating the request is free. |
Page reading and search are different activities, so “Page retrieved” can correctly appear alongside “no completed web search.” A source citation links to supporting material; its presence is not a guarantee of truth. Check dates, the exact entity or product variant, and whether the cited text actually supports the claim.
Chat: images, files and dictation
Attachments are shared only with the selected compatible providers after review. Original files are not carried into later turns or Council.
- Use the attachment control and wait for reading to finish. Check the displayed supported formats, size and page limits before uploading.
- Review each file and the exact recipient/model preview. Remove sensitive pages and unnecessary images before confirming.
- Ask a specific question about the supplied file. For long text and decision-focused reading, use the dedicated Document reader.
- For image preparation, use the image optimise/enlarge controls where available; inspect the result before attaching. Enlargement cannot restore facts absent from the original.
- For dictation, grant microphone permission only when you want to dictate, review the transcript and stop recording before sending.
Troubleshooting files and dictation
- File rejected: check the displayed type/size/page limits; split, compress or provide text. A scanned PDF may need OCR before use.
- Unreadable or password-protected document: unlock locally and export readable text, then review it.
- Microphone unavailable: check browser/site permission and device input; typing is always available.
- OpenRouter selected: remove files or choose another compatible provider.
More detail and practical checks
Optimise and enlarge images
- Select an image within the upload size limit.
- Click Optimise image beside it. Processing takes place in your browser.
- Check the size-reduction notice. If the image cannot be made smaller, the original is retained.
- Click the thumbnail to open Image preview. Keyboard users can focus it and press Enter or Space.
- Use Actual size to inspect detail and scroll where necessary. Use Fit to screen to return to the fitted view.
- Close with ×, Escape or the backdrop outside the preview.
Optimisation can resize the longest edge to 2,400 pixels and convert the image to JPEG. It can soften small text and replace transparency with white. Inspect diagrams, labels and screenshots before sending. The preview shows the version currently prepared for upload, not a retained original-versus-optimised comparison.
An image already over 10 MB is rejected before this tool can optimise it. Resize it using a trusted tool on your device, then select it again. There is no built-in PDF, Word or general file compression.
Microphone dictation
- Click Microphone.
- Read the browser-speech-service notice and agree if you want to proceed.
- Allow microphone access in your browser when prompted.
- Speak your question. Review the words placed in the composer.
- Click the microphone control again to stop if it is still listening. Correct names, numbers and punctuation.
- Click Send yourself. Dictation does not automatically submit a question.
This feature converts speech into editable text; it is not a real-time voice conversation, audio upload or spoken-answer feature. Your browser’s speech service may process audio externally. Ortivo does not itself record or upload an audio file for this feature.
Recognition stops when you leave the view or page, the page is backgrounded, or the listening time limit is reached. Browser support and device permissions vary. If recognition is unavailable, type your question. If it is blocked, check browser and operating-system microphone permissions. Never dictate API keys or passwords.
Projects: organise work and reuse sources
Projects organise related work, notes and saved sources. A saved project is not proof that every AI request includes its contents.
- Open Projects and create or select a project. Give it a recognisable title and concise notes.
- Save useful website or document sources to the intended project using the reader’s save controls.
- Reopen a saved source in the appropriate reader. Check that it is still current before using it.
- Use the visible context controls and request preview to decide what accompanies a task. Include only the context needed.
- Keep decisions in the notebook and reusable instructions in My prompts, rather than duplicating full conversations in every note.
Troubleshooting projects
- Missing item: check the selected project and refresh only after saving your draft.
- Source changed: read the current public page again; stored extracts may be older.
- Context absent from an answer: inspect the preview and explicitly supply the relevant text; do not assume notes are automatically attached.
Open Projects · Open Documents · Open Website · Open Decision notebook
Projects: Document reader
Read extracted document text with a clear question or a reading lens. Extraction and an AI answer are different steps.
- Open Document reader and choose a supported file. Wait for extraction and inspect the extracted source text.
- Choose Audit claims, Find decision hinge or Extract commitments, or write your own question.
- Choose a connected provider and available model. Review the exact source text and question in the paid-request preview.
- Send after review. Check the answer against the original document, especially tables, figures, scanned pages and commitments.
- Save the source to the correct project when useful. Record a decision separately in the notebook.
Troubleshooting Document Reader
- Empty extraction: try a text-based file or OCR locally; do not treat an empty extract as the whole document.
- Text too long: reduce the source to relevant passages and preserve their context.
- Unexpected cost: the preview includes the entire extracted source text, not just the visible viewport.
My prompts: browse, personalise and save
Browse 48 starter templates across 11 categories, then turn a useful one into a prompt that fits your task.
- Open My prompts. Browse categories or search for the outcome you need. Switch to My saved for your own prompts.
- Open a template and fill its required context fields. Review the complete prompt preview for unresolved placeholders and sensitive information.
- Prepare a Chat draft, or use Prepare Research Agent goal for supported research templates. This fills a draft and does not send an AI request.
- In My saved, create, edit or duplicate a reusable prompt. Use {{variable}} placeholders for details that change between tasks.
- Search your saved prompts, use pagination and export a backup when useful. Avoid saving API keys or private source documents in templates.
Troubleshooting saved prompts
- Preview blocked: complete required fields and remove unresolved placeholders.
- Draft too long: shorten it; Chat accepts up to 16,000 UTF-8 bytes and the Research Agent goal up to 2,000.
- Saved limit: a prompt is limited to 12,000 UTF-8 bytes, up to 20 distinct variables and 50 saved prompts.
- Existing draft warning: review and copy it before replacing it.
Settings: personal and project memory
Memory can hold short facts for reuse. Scope and inclusion should be deliberate; do not use it as a password store.
- Open Settings and then Memory using the context/settings controls.
- Review existing personal/project facts and choose the intended scope before saving a new fact.
- Keep each fact short and factual. A full answer may exceed the 600 UTF-8 byte limit for one memory.
- Use the visible memory controls to decide what accompanies a Chat request. Inspect the preview and recipient before sending.
- Review, edit or remove outdated facts through the memory controls. Help does not automatically read memory contents.
Troubleshooting personal and project memory
- Fact too long: keep one short fact under the displayed byte limit.
- Wrong project context: check scope and selected project before use.
- Old fact repeated: update the memory and start a fresh conversation if old turns already include it.
Settings: My brief and context
My brief stores reusable context. Attach it deliberately and inspect which providers will receive it.
- Open My brief under Settings. Write only the stable context relevant to your work and save it.
- In Chat, enable Attach my brief when you want it included in that conversation.
- Review the provider/recipient line and other context controls. Turn off attached brief before web search.
- For project-specific tasks, supply the relevant source text explicitly rather than assuming all project notes are automatically attached.
- Keep secrets and unnecessary personal information out of reusable context.
Troubleshooting your brief
- No brief attached: save a non-empty brief and enable the Chat control.
- Search blocked: turn off Attach my brief before search.
- Unexpected assumptions: update the brief and start a fresh conversation if earlier turns already contain old context.
History: saving, reopening and exports
Saving is off by default. Private-session conversations disappear when you leave the page; enabled saved history belongs to your Ortivo account.
- Choose the save-history setting before starting a conversation. Changing it after a conversation has begun starts a new conversation after confirmation.
- Open History to view saved conversations. Reopen the intended provider’s conversation before following up.
- Use export to download your saved conversations and keep the file securely.
- Use deletion controls carefully: active storage deletion may be permanent, while encrypted backups follow their own expiry.
- Save decisions and research findings in the notebook for a concise record rather than relying on a long transcript.
Troubleshooting saved history and exports
- History empty: you may have used a private session or a different account.
- Attachments missing: originals are not saved as reusable context for later turns.
- Private draft lost: the helper cannot recover page-memory content after reload.
Costs, token usage and practical limits
Each answer shows the model and provider-reported input/output token counts. Tokens are units of model input and output, not a direct currency amount. These numbers are not an invoice and may not itemise all search, cached-input or other provider charges. Your provider dashboard is the source of truth.
- Comparison sends one request per selected provider; Council stages add requests.
- Follow-ups resend available conversation context. Long conversations can cost more.
- Images, PDFs, extracted document text and retrieved pages can increase input usage substantially.
- Search can add tool charges and multiple search uses.
- Failed or timed-out requests may still incur provider charges.
Use one provider for simple tasks, keep briefs focused, ask concise questions and start a new conversation when old context is unnecessary. Check provider usage and spending controls regularly.
Current plugin limits include 100 chat/Council requests per user per UTC day, up to 20 exchanges in a conversation and an output allowance of 2,048 tokens per request. The daily request limit is not a dollar spending cap. Question and request-size limits can also apply. “Output limit reached” means the answer may be incomplete; a new follow-up is another request and may incur another charge.
AI Council: review, challenge and decide
Council reviews successful answers from your latest Chat request. Each review stage is an additional paid request, with a preview of the material being shared.
- Ask your question in Chat first. Keep the successful answers you want to examine on this page.
- Open AI Council. Choose which AI should review and select an available reviewer model. Only successful answer sources are selectable.
- Choose Evidence check, Stress test, Decision hinge or Action plan. Edit the instructions to state the decision you are trying to make.
- Check the source selections and exact request preview. Approve only the material and provider you intend to use.
- Read the result for unsupported assumptions and practical next steps. Advanced stages may include earlier Council results; check their preview too.
- Save the decision, key assumption, smallest useful test and revisit condition in the Decision notebook.
Troubleshooting AI Council
- No sources: return to Chat and complete at least one successful answer. Reloading a private session loses those answers.
- Reviewer unavailable: connect the provider, refresh models and select an accessible model.
- Original file missing: Council receives answer text, not the original attachments; verify important claims against the file yourself.
- Agreement is not verification: use source evidence or an independent test.
Open Council · Open Chat · Open Decision notebook · Open Settings
Projects: Decision notebook
Keep the decision and its reasoning together so you can revisit it when evidence changes.
- Open Decision notebook and add a record, or save from Council or Research Agent.
- Record the decision question, evidence, chosen action and uncertainty. Use Add decision hinge & review prompts for a structured starting point.
- State the key assumption, smallest useful test and the condition that would make you reconsider.
- Save changes. Use search and status filters to find evidence-only, decision and outcome records.
- Add the observed outcome later. A status reflects which fields are filled; it does not verify evidence quality.
Troubleshooting Decision Notebook
- Unsaved changes: save before navigating away or reloading.
- No matches: clear search and status filters.
- Private research disappeared: export or save the run before leaving the page.
Research Agent: brief, plan, research and report
A bounded run can use up to four paid requests: one planning request, two research requests and one report request. That is a request limit, not a spending cap.
- Open Research Agent. Use the brief builder to define the decision, audience, scope and desired evidence, or write a focused goal under 2,000 UTF-8 bytes.
- Select a connected OpenAI or Claude provider and a search-compatible model. Include exact public HTTPS URLs when a particular site matters.
- Review and approve Create research plan: one paid request. Edit the two proposed questions before approving research.
- Approve the plan for up to three further requests. Inspect scope and domain warnings; off-scope or missing source URLs may pause the run for your review.
- Watch request usage and the evidence ledger. Stop after current request prevents later requests but cannot guarantee cancellation or refunds for the active one.
- Keep the page open. Export the report and evidence ledger, or save useful results to the Decision notebook before leaving.
Troubleshooting Research Agent
- Model missing: connect OpenAI or Claude and refresh model choices.
- Paused after research: inspect the evidence and scope warning; revise the goal or questions rather than assuming the report is complete.
- No report: check the failed stage and provider dashboard before approving another paid attempt.
- Unsaved run lost on reload: use export or notebook saving before leaving. No background completion is promised.
Open Research Agent · Open Sources · Open Website · Open Decision notebook
Research: Website reader
Read one accessible public page and inspect the extracted text before asking an AI about it.
- Open Website reader and enter the exact public HTTPS page URL.
- Fetch/read the page and inspect the extract and source address. This does not crawl an entire website or sign into private pages.
- Choose a reading lens or write a question, select a connected model and review the complete text before approving an AI request.
- Check important claims against the original page. Save useful sources to a project and record decisions separately.
Troubleshooting Website Reader
- Blocked or empty page: the site may require sign-in, scripts or access it does not grant to Ortivo. Use permitted text or a different public source.
- Wrong page: provide a specific article/detail URL rather than a homepage.
- Site audit request: one page is not a complete crawl; use a list of specific pages and verify site-wide claims separately.
Research: Web sources and You.com
Web sources retrieves search results or public page contents through a separate You.com connection. It is separate from the four chat AI providers.
- Open Web sources. Connect You.com in its connection area if retrieval is not configured.
- Enter a focused query or exact public URL, then review the retrieval request and any service charges.
- Inspect result URLs, dates and contents. Add relevant sources to the selection tray.
- Use the available handoff/save controls to work with chosen material. Review any AI request separately; selecting sources alone does not send them to an AI.
- Keep the source address and retrieval context so you can verify what evidence was available.
Troubleshooting Web Sources and You.com
- Not connected: use the You.com connection controls, not an OpenAI or Gemini key.
- Weak results: narrow the query, include dates or use the exact public page URL.
- Retrieval succeeded but no AI answer: retrieval and generation are separate actions.
Research: Scheduled research
Scheduled research can create private reports on a recurring schedule after you review and enable it. Future runs can incur provider charges.
- Open Scheduled research. Create a paused draft with a clear goal, provider/model and frequency.
- Review what will run, who receives the request and expected costs. Check the site’s displayed schedule/timezone.
- Enable only when you want recurring requests. Keep the scope small and review provider budget controls.
- Read reports and check the last/next run status. Pause or disable the schedule when no longer needed.
- Use manual Research Agent when you need to approve each plan and report stage.
Troubleshooting scheduled research
- Overdue run: WordPress scheduling depends on hosting/cron and site activity; exact execution time is not guaranteed.
- No report: inspect the last run status and provider billing/model access; avoid repeatedly enabling duplicates.
- Duplicate reports: check for overlapping active schedules and pause extras.
Troubleshooting: guided checks and safe recovery
Check the exact failing feature, the step that failed and whether any request may already have reached the provider. No automatic paid test or retry is run by Help.
- Use Check workspace for read-only connection configuration and visible UI checks. A configured connection is not a live health test.
- If the session expired, copy unsaved drafts and export results, then sign in again or reload.
- For authentication, quota and model problems, open Settings and follow the matching provider guide. Check the provider dashboard/status.
- For file or website problems, inspect extraction before sending to AI. For Council, make sure successful Chat answers exist in this page session.
- Copy the redacted support summary if you need further help. Review it before sharing; add a short description of expected versus actual behaviour, without keys or private documents.
Troubleshooting guided recovery
- Do not repeat Send while a request is running.
- If a request timed out or returned unreadable output, verify provider usage before retrying.
- Basic help stays local and available without a connected AI. Optional AI explanation has a separate exact-request review.
Navigation, mobile and accessibility
The adjustable sidebar groups tools into Chat, Projects, Research, Prompts, History, Settings and Help. AI Council is available from Chat and its own URL.
- Use the sidebar toggle to expand or collapse navigation. On narrow screens, open the menu and select a section.
- Use the section tabs for related tools: Projects includes readers/notebook; Research includes Agent, Website reader, Web sources and Scheduled research.
- Bookmark a tool’s own URL. Browser Back and Forward return between visited workspace tools. Chat is at the homepage; /workspace/ redirects there.
- Use keyboard Tab and Enter for controls and Escape to close Help. Help retains this page’s conversation until Clear or leaving the page.
- If a control is hidden, expand the sidebar or open the feature from this Help directory.
Troubleshooting navigation and mobile access
- Layout cramped: collapse the sidebar and check browser zoom.
- Dialog blocks a tool: close it with its close button or Escape.
- Unavailable feature as a guest: sign in to use private workspace tools.
Google Drive import
Google Drive import is available to signed-in Ortivo users. Open Chat, choose +, then Choose from Google Drive. A connection panel shows loading progress. When ready, select Continue to Google to open authorisation. Choose the Google account containing the document you want to import and review the requested permission.
Choose one Google Doc, Sheet, PDF, DOCX, XLSX, TXT, Markdown, CSV, JPEG, PNG or WebP file. Import one file at a time; a message can contain up to three attachments, 10 MB each and 20 MB total. Text and extracted Office content are limited to 500 KB per file. In + → More tools → Google Drive permissions & privacy, choose Preserve page layout (PDF) for Google Docs/Sheets, or Extract text and spreadsheet cells for analysis. PDF export retains exported page layout and images; comments are omitted, and large sheets may span pages. DOCX imports main text only. XLSX imports sheet names, cell addresses, values and formulas; formulas are shown without execution, and charts/images/most formatting are omitted. Legacy DOC/XLS, password-protected Office documents and unsupported image types must be converted first. Review the attachment and select compatible AI providers before Send. Import does not automatically call an AI. Large extracted text can exceed a provider model context limit. Computer uploads support the same PDF, Office, image and text formats.
Disconnect Drive clears the token from this page; it does not revoke the Google grant or remove already imported attachments. Remove the attachment, start New chat or leave the page to clear it. Google Account connections provides full grant revocation. See the privacy policy for details. If Google tools cannot load, use a computer upload while the connection is investigated.
Web and News search without personal AI keys
In Chat, open +, then Web search. Enter a query and choose Web or News. Optionally select a date range and country preference, then click Search. Brave results appear inside Ortivo with publishers, available dates, extracts and source links. Open a source to visit the original page in a new tab. Close the search box with × or by clicking outside it.
No personal AI-provider connection is needed. Ortivo funds searches through its Brave account and applies daily account and monthly site request limits. Search terms and filters go to Brave; existing chat history, uploaded files and personal AI keys are not included. These are search extracts, not AI-written answers. Dates may reflect updates, coverage varies and publisher paywalls apply. AI-assisted Web on in Chat and You.com Web sources remain separate tools.