YOUR AI TEAM. ONE DESKTOP WORKSPACE.

Your sources. A team to think with.

Bring the question, choose the roles and shape the next step together. OptiVerse Studio is building a multi-agent workspace, with meeting and reading tools to carry useful context into the work.

Explore the multi-agent flow AI Tools business orders

OptiVerse Studio Multi-agent workspace in development See AI team plans

Start with a question

What should we build next?

Your sourcesMeeting notes · Research documents
  • MMiraResearch
  • TTheoDesign
  • QQuinnReview

A direction worth exploring

Compare the evidence. Shape a proposal. You choose the next step.

Illustrative team concept · planned
  • Agent roles that work together
  • Meeting capture, transcripts and summaries
  • Document translation and source checking

THE TEAM IN ACTION

From a question to a direction.

Follow a concept of how your team could research, discuss and refine a proposal—with you in control.

Interaction concept · in development
  1. 1Bring a question
  2. 2Compare directions
  3. 3Confirm source access
  4. 4Improve the proposal
  5. 5Review the revision
  6. 6Choose a version
The team finds a direction in the sources, develops an approach and improves the proposal through feedback. Ask follow-up questions, request changes or keep exploring. This is an interaction concept in development.

Current features & future plans

AI team and workspace feature previews

Explore the planned AI team workspace, results and work management, alongside reading tools implemented in the development build. Each feature carries its own status.

Work directly with your AI team.

Discuss ideas with different roles, adjust the members and decide how to continue—from exploration to a plan and shared work.

  1. Shape the team around the question PlannedAlongside

    Ask members directly, follow up and add your own ideas. Add members or adjust roles and skills as needed, with their conversations and status visible.

  2. Connect the AI tools you use PlannedAlongside

    Planned connections include Codex with a ChatGPT subscription and Claude Code. Accounts, quotas and billing follow provider rules. Material given to these cloud AI services is sent to the provider; integration support still needs validation.

  3. See what a claim is based on PlannedAlongside

    Inspect the note, brief or file version a member cites, and distinguish supported claims from judgments that need checking. Sources that could not be read are identified.

  4. Handle decisions in one place PlannedAlongside

    Authorized work can continue. Decisions and requests for additional permission appear in “Needs me,” where you can inspect the scope, allow once, deny or add instructions.

  5. Follow progress and step in PlannedAlongside

    See whether work is still running separately from the version of its result. Pause or request a stop when needed; a stop remains marked as requested until confirmation arrives.

Read in two languages. Keep the evidence close.

Open a document, compare its Traditional Chinese translation with the original, keep useful passages and ask questions with source links. These tools are implemented in the development build; AI team integration remains planned.

Explore the reading guide

  1. Bring your documents into one reader Available in development

    Import PDF, Word (.docx), Markdown and text files for reading and source-based questions.

    How it works

    Files are stored on your device. Scanned PDFs without a text layer can be viewed and used with manual notes; translation, extraction and questions require readable text.

  2. Compare the original and its translation Available with limits

    Switch between Original, Translation and Side by side to check wording as you read.

    How it works

    Translation currently targets Traditional Chinese and uses the built-in local model. Completed passages are saved, so you can stop and continue translating later.

  3. Translate a PDF page in its original layout Available with limits

    Translate this page or the whole document. PDF translation uses the original page’s text areas to keep its layout recognizable.

    How it works

    Layout preservation applies to PDFs. Dense translated text may shrink or be clipped, with a warning. Word, Markdown and text use a flowing bilingual view rather than preserving the original pagination.

  4. Follow citations and keep useful passages Available with limits

    Highlight a passage or quote it into notes with a link back to the source. Inspect citations in document answers.

    How it works

    The reader can follow recognized numbered references such as [1] and existing PDF links. Answer citations help you inspect source passages; you still need to check whether a claim is supported.

  5. Turn reading into study notes and questions Available with limits

    Generate study notes with source links, or use Ask for This document or All documents.

    How it works

    Study notes use the built-in local model. Ask uses the selected provider; choosing a remote service sends the question and relevant excerpts to it. Each question uses the chosen documents, without conversation memory.

Reading extensions still planned

  • Read EPUB books

    EPUB import remains planned. The current reader accepts PDF, Word (.docx), Markdown and text files.

  • Use familiar names and terminology

    Apply a shared glossary across reading, summaries and translation to reduce variations in names and technical terms.

  • Ask across selected papers and discussion records

    Combine selected documents and discussion records in one question, with page or time references where available. Current document Ask and meeting Ask remain separate.

Review and refine the result.

See who contributed and which sources were used. Request changes, revisit retained drafts and choose the version to accept.

  1. Know who wrote it and what they used PlannedAlongside

    Results name their author, version and the source versions used, so you can check the basis for the work.

  2. Accept this version or request changes PlannedAlongside

    Give feedback on the current version or choose to accept it. Continue refining new drafts as needed.

    How it works

    Give feedback on the version you are viewing or explicitly accept it. A later version needs its own acceptance rather than inheriting your earlier decision.

  3. Revisit retained versions PlannedAlongside

    Open a retained earlier version without changing it. Continuing from it creates a new draft and preserves the earlier content.

  4. Check delivery when you need it PlannedAlongside

    Save accepted work to your chosen folder and check that it arrived successfully.

    How it works

    Save an accepted result to the chosen folder and track whether delivery succeeded. A failed save does not remove the accepted version or its acceptance record.

Recover context and manage what carries forward.

Review recent work, inspect the information kept for later and decide whether it should still be used.

  1. Review a day or a week PlannedAlongside

    Gather included meetings, reading and tasks into a short recap of recent developments and work that remains open.

  2. See where a memory came from PlannedStage 3

    Open stored information about projects, people and topics, inspect its sources and decide whether it is still useful for future work.

  3. Correct, disable or delete a memory PlannedStage 3

    Edit stored information or stop its future use within a chosen scope. Deletion is a separate action with its own supported scope; it does not mean deleting the original sources.

  4. Follow a topic over time PlannedStage 2

    Trace a topic through the meetings, papers and notes you have included, in time order, to see how the discussion developed or changed.

Follow the discussion in your language.

Compare original and translated transcripts, check important terms and prepare subtitles for later review. Live translated captions remain a separate planned capability.

  1. Translate transcripts and summaries PlannedAlongside

    Translate transcripts and summaries, preserving available transcript timestamps for checking against the recording.

    How it works

    Read the content in your preferred language, with available timestamps preserved in transcripts. Content already in that language is not translated again; Simplified-to-Traditional Chinese conversion runs on the device without a separate translation.

  2. Read both languages side by side PlannedAlongside

    Compare the original and translation line by line to check uncertain wording, or switch to a single-language view.

  3. Export subtitles for the recording PlannedAlongside

    Export SRT or WebVTT subtitles, with both languages when needed.

    How it works

    Export SRT or WebVTT subtitles using the transcript’s timing and complete-sentence segments. Choose bilingual subtitles when needed, with the language identified in the file name.

More features and advanced use

  1. Use your team’s names and terminology PlannedAlongside

    Keep names, acronyms and product terms in a glossary for transcription, summaries and translation. Import a CSV or review names suggested from your discussions.

  2. Flag wording you want to avoid PlannedAlongside

    List unwanted terms with preferred alternatives and a reason. Occurrences in summaries or translations are flagged for review rather than silently rewritten.

  3. Find gaps and inconsistent translations PlannedAlongside

    Check language, missing lines, glossary terms and unwanted wording, with inconsistent translations grouped together. Lines that fail a check retain the original text and can be translated again individually.

  4. Correct misheard names and terms PlannedAlongside

    Use find and replace in a transcript, saving a new version that stays linked to the recording. Confirmed names can also join the vocabulary for future recordings.

  5. Follow translated captions while recording PlannedAlongside

    Supported computers can show a quick translation grouped into sentences while recording. A second translation uses the complete discussion afterward, so live wording may change.

Return to the project with the context intact.

Bring related sources and open work together so you can find earlier decisions and see what still needs attention.

  1. Choose the material that belongs together PlannedStage 2

    Add related meetings, notes and tasks to a project, then review its decisions, open commitments and unanswered questions in one place.

  2. Keep the basis for tasks and dates PlannedStage 2

    Trace a task back to its source and see whether its owner and due date were stated or inferred.

    How it works

    Follow a task back to the content that raised it, and see whether its owner and due date were stated or inferred. Regenerating a summary preserves completed-task status.

  3. Review potentially outdated or conflicting information PlannedStage 2

    See separate flags for possibly outdated information, missing support and conflicting claims, alongside their evidence. Choose what to keep, correct, dismiss or replace without rewriting the originals.

  4. Understand why sources are related PlannedStage 2

    Open related meetings, decisions or tasks and see why they are connected. Incomplete source coverage is identified.

  5. Schedule confirmed tasks PlannedAlongside

    Confirm the task, owner and due date before placing it on your calendar as you choose, keeping a link to the original discussion.

Know what is happening and when to step in.

Choose the material a task can use, inspect reported progress and usage, and handle decisions or additional permissions in one place.

  1. Choose sources for this question PlannedStage 1

    Select meetings, notes and tasks and check the scope before asking. Answers cite the passages actually used and identify unreadable material or insufficient evidence.

  2. Look back over the work PlannedStage 1

    Look back over sources, processing location, progress and results. Unreported information stays unknown.

    How it works

    Inspect available records of purpose, sources, processing location, progress, results and usage. Unreported details stay unknown, and cancelled or retried work is checked before a result is treated as current.

  3. Know the account and where data goes PlannedStage 3

    Connections to Codex with a ChatGPT subscription or Claude Code are intended to show the account, billing mode and data destination. Cloud processing sends relevant material to the provider; support depends on integration testing and provider rules.

  4. Separate usage from remaining allowance PlannedStage 1

    Check available usage and remaining account allowance, with the source and update time.

    How it works

    See token processing rate, recorded usage, context in use and remaining account allowance as separate readings, with a source and time. Unreported values stay unknown; other work on the account may affect its remaining allowance.

More features and advanced use

  1. Save a way of working for next time PlannedStage 3

    Keep a well-defined, repeatable task with its required material, expected result and limits. Preview what it would produce or change before deciding to use it.

  2. Manage your saved preferences PlannedStage 3

    Preferences you write or accept show their scope, source and last confirmation. Disable or remove them to change how later work uses them.

  3. Continue from a terminal PlannedStage 3

    Run saved workflows and exports from a terminal or script, using the application’s limits and the same activity log to inspect the result.

Bring your sources into the work.

Collect recordings, documents and excerpts with their origins, then select what to use for a question or share with the team.

  1. Search the material you have organized PlannedAlongside

    Store recordings, papers, Word files, e-books and Markdown on your device and search content that has been imported and indexed. Adding it to the library does not automatically grant the team access.

  2. Collect first, then choose how to use it PlannedStage 3

    Collect links, excerpts and files with their origins, then choose what to use in a project or question.

    How it works

    Keep links, excerpts and files with their origins in a reference inbox, then select them for a project or question. Capturing a page does not crawl the pages it links to.

  3. Add existing transcripts and subtitles PlannedAlongside

    Import supported meeting transcripts, SRT or WebVTT files with available timestamps, ready to use for summaries, translation and questions.

More features and advanced use

  1. Keep web excerpts with their source PlannedStage 3

    Save an article or page excerpt to the inbox with its original source, then choose what to bring into your work later.

  2. Preview notes before importing PlannedStage 3

    Before adding a Markdown folder, review the proposed import and resolve conflicts. Importing leaves the original files unchanged.

  3. Inspect storage and source records PlannedStage 2

    See storage use, attachment references and broken links without automatic deletion. Compare a retained note version before restoring it.

These are interface schematics. Reading features exist in the development build; other experiences are planned as labeled. Public release still requires validation. External AI services receive relevant material when selected.

See AI team and feature plans

WORK AS A TEAM

Bring different AI roles together.

A planned workspace for researching, designing and reviewing together. Give the team a question, follow the discussion and choose the next step.

Illustrative interaction concepts · in development

Start with your sources.

Choose the material your team can use, then follow a claim back to the passage behind it.

Meeting notes · Research documentsFrom your sources
“Make the first question easy to ask.”
Source linked

Shape the team around the question.

Bring research, design and review into the same discussion, with roles you can adjust as the work develops.

MMiraResearch
TTheoDesign
QQuinnReview
One question. Three perspectives.

Make the result better, together.

Let the team question a draft, propose improvements and carry your feedback into the next version.

Proposal v1Import a source
Proposal v2Guide the first questionRevision shown

You choose what happens next.

Review the proposal, ask for changes or accept a version when it meets your needs.

Awaiting your reviewYour call

Keep refining, or choose the version to continue with.

Accept this versionRequest changes

A ROLE FOR EVERY QUESTION

Give each AI role a clear job.

Start with the work you want to move forward. Explore how a research partner, designer or reviewer could help you think it through.

Research partner

Compare findings, follow citations and ask where the evidence is still thin.

Explore more use cases

Design partner

Turn selected research and interview notes into a proposal you can question and refine.

Explore more use cases

Independent reviewer

Check a draft against the brief and find what needs a closer look.

Explore more use cases

Discussion partner

Revisit a recorded discussion, check decisions against the transcript and keep unresolved questions visible.

Explore more use cases

Fictional examples of planned interactions · in development

OptiVerse Studio
You · The question

Compare these two research papers. What evidence supports each approach, and what remains unclear?

MMira

Paper A tests first-time users; Paper B studies experienced teams. Their results may reflect different starting points. Check the samples before comparing the conclusions.

Selected sources · Research paper A · Research paper B
A possible result

Evidence comparison

Evidence comparedOpen questions
OptiVerse Studio
You · The question

Use this brief and the interview notes to propose a simpler first-use experience.

TTheo

Begin with one source import, then guide the first question. Keep the source visible beside the answer. The interview notes suggest new users need clearer starting points.

Selected sources · Research brief · Interview notes
A possible result

First-use proposal

Sources connectedProposal draft
OptiVerse Studio
You · The question

Review proposal v1. Where might a new user get stuck, and what should we revise?

QQuinn

The draft shows how to import a source, but not what to ask first. Add a starter question before we call the flow complete.

Selected sources · Proposal v1
A possible result

Draft review

Gap identifiedRevision suggested
OptiVerse Studio
You · The question

Recap this recorded discussion. Which decisions did we make, and which questions are still open?

MMira

We agreed to simplify the first import and keep source references visible. The first question is still undecided; bring it back to the next review.

Selected sources · Meeting transcript
A possible result

Discussion recap

Decisions collectedQuestions still open

ONE DIRECTION. COORDINATED WORK.

You set the goal. The team carries it forward.

The planned experience connects two loops: you and a coordinator keep the direction clear, while specialists work on focused tasks, check results and revise. Their work returns as one result you can inspect.

Illustrative coordination concept · In development. Roles and integrations may change.
OUTER LOOP · DIRECTION & DECISIONSPlanned experience
YOU · THE SHARED GOAL

Make the first step of a research tool easier.

Use the selected interviews and research brief. Ask before expanding access or changing the scope.

  1. 01Set the goal
  2. 02Shape the brief
  3. 03Review the evidence
  4. 04Choose what follows

INNER LOOP · FOCUSED EXECUTION

Brief, work, check, refine.

Shared context · Separate assignments
COORDINATOR · KEEPS THE BRIEF CONNECTED

Turn the question into bounded assignments.

The coordinator brings together the goal, selected context, ownership and what a useful result must show.

  1. MMiraResearch

    Find which part of getting started caused trouble in the interviews.

    ↳ Evidence notes + source passagesTask defined
  2. TTheoDesign

    Draft a guided first question within the agreed scope.

    ↳ A first-step proposalTask defined
  3. QQuinnIndependent review

    Check the proposal against the brief, sources and open questions.

    ↳ Findings + revision requestsReview criteria set

A check can send work back. Clarify missing context before starting dependent work.

ONE RESULT TO INSPECT

A brief the team can work from

The same goal, with clear responsibilities, limits and checks.

COORDINATOR · KEEPS THE BRIEF CONNECTED

Let independent tasks move together.

Research and design can progress separately. Each specialist keeps its own work visible; dependent checks wait for the material they need.

  1. MMiraResearch

    Find which part of getting started caused trouble in the interviews.

    ↳ Evidence notes + source passagesReading selected sources
  2. TTheoDesign

    Draft a guided first question within the agreed scope.

    ↳ A first-step proposalDrafting the approach
  3. QQuinnIndependent review

    Check the proposal against the brief, sources and open questions.

    ↳ Findings + revision requestsWaiting for the draft

A check can send work back. Only independent tasks run in parallel; dependencies remain visible.

ONE RESULT TO INSPECT

Evidence notes + a proposed first step

The coordinator brings the separate findings back to the same brief.

COORDINATOR · KEEPS THE BRIEF CONNECTED

Return a gap to the person who can fix it.

The reviewer finds that the draft assumes more interviews than the selected sources support. The coordinator sends that part back for revision.

  1. MMiraResearch

    Find which part of getting started caused trouble in the interviews.

    ↳ Evidence notes + source passagesSource passages ready
  2. TTheoDesign

    Draft a guided first question within the agreed scope.

    ↳ A first-step proposalRevision requested
  3. QQuinnIndependent review

    Check the proposal against the brief, sources and open questions.

    ↳ Findings + revision requestsGap identified

A check can send work back. Keep the failed check and the next revision connected.

ONE RESULT TO INSPECT

A proposal with a visible correction

The recommendation narrows; the uncertainty stays in the result instead of disappearing.

COORDINATOR · KEEPS THE BRIEF CONNECTED

Hand back the work and the evidence together.

The coordinator combines the revised proposal, source passages, checks and open questions into one result for you to review.

  1. MMiraResearch

    Find which part of getting started caused trouble in the interviews.

    ↳ Evidence notes + source passagesEvidence linked
  2. TTheoDesign

    Draft a guided first question within the agreed scope.

    ↳ A first-step proposalRevision included
  3. QQuinnIndependent review

    Check the proposal against the brief, sources and open questions.

    ↳ Findings + revision requestsChecks recorded

A check can send work back. Passing checks and unresolved questions are reported separately.

ONE RESULT TO INSPECT

A clearer first step · proposal v2

A guided opening question, the interview evidence behind it, and a next step to test with new users.

Back to your direction. Inspect the sources, request changes or choose the next step. A finished task does not make the decision for you.

See the team plans

Bring useful context into the work

Meetings and reading support the bigger picture.

Capture what was said and understand what you read. These development tools help you keep the evidence close as multi-agent collaboration takes shape.

Implemented in the development build

Keep the meeting, then find what matters.

Capture audio, review the transcript and summary, and ask about the meeting with links back to the source.

  • Record or import meeting audio
  • Review transcripts and summaries
  • Ask questions and inspect source passages
View the meeting workflow Open the recording guide
Implemented in the development build

Read the document, then check the evidence.

Read alongside a Traditional Chinese translation, keep notes and ask questions with source links. PDF translation can follow the original page layout.

  • Compare original and translated text
  • Keep highlights and study notes
  • Ask about documents and follow citations
Try the reading demo Open the reading guide
Explore how sources, discussion and revisions stay connected

THE WORK, CONNECTED

Turn your context into a clear next step.

A planned workspace where your sources, your AI team and the next version of an idea stay part of the same conversation.

Illustrative AI team workflow · in development
  1. 01Bring context
  2. 02Compare ideas
  3. 03Refine together

01Keep the source close

Start with what you already know.

Bring a question and the material behind it into the discussion. The planned team experience keeps the relevant passage close to the idea it supports, so you can see where a recommendation comes from.

Explore research use cases
Interview notes ↗

What held people back?

Early interviews about starting a new research project.

“I have the notes. I just don’t know what to ask first.”

Interview 02 · selected passage

Mira · Research perspective

A useful first question may matter more than adding another import option.

↗ Interview notes · 02

02Think across perspectives

Give the question more than one point of view.

A research partner follows the evidence. A designer explores an approach. A reviewer looks for gaps. Adjust the planned roles around the work and add your own judgment as the discussion develops.

Explore the roles in practice
A team shaped around the question
M
MiraResearch

The interviews point to the first question as the main obstacle.

T
TheoDesign

What if the first screen offered a useful starting question?

Q
QuinnReview

Test that direction with new users before widening the scope.

The recommendation and the uncertainty stay visible.

03Make the next version better

Keep the feedback. Move the idea forward.

Ask for a clearer argument, question an assumption or take another direction. The planned workflow brings the discussion back to a revised proposal, with you choosing the version to continue with.

See the AI team plans
You · Feedback on v1

“Make the first step clearer. Keep the evidence and the open question.”

Proposal · v2Revision shown

A clearer first step

Earlier direction

Start by importing a source.

Revised direction

Start with a guided question.

Ready for your review

Request another change, or choose this direction.

Questions

A few essentials.

Understand the product, availability and data handling. Find detailed guidance in the docs.

Read the docs

What is OptiVerse Studio?

OptiVerse Studio is an AI team desktop workspace in development. Discuss directly with different roles, adjust members and skills, and work from exploration through design and execution. Existing recording, transcript and summary capabilities will join that workflow in stages.

Can I download it now?

OptiVerse Studio does not have a public installer yet. For the separate enterprise product, use the AI Tools business order application to order 語音轉錄既資訊知識整合平台. Enter and review your company and contact details, then submit. 富宇資訊科技有限公司 (OptiVerse Technology Ltd.) sends the order confirmation and provides the licensed software download and License Key. AI Tools business order application

Will my data stay on my computer?

Studio defaults to local recording, transcription and built-in-model summaries. Selecting external AI sends relevant material to that service. The OptiVerse Studio AI team also plans to use external services; destinations depend on the features and services selected. Deleting local content does not remove exports, backups or material already sent to external services.

What would you like to do with an AI team?

Tell us about your work, or ask about OptiVerse Studio development.

Email us