Clara

Clara keeps a professional case moving between documents, conversations and drafts.

Use Clara when the useful information is split across files, notes, calls and half-formed views. She keeps the trail clear, shows what still needs review, and helps prepare drafts that can be checked before anyone shares them.

Who does what

Clara prepares the intelligence layer. The consultant keeps the professional judgement and decides what is ready to use.

Clara's intelligence

Reads the materials, keeps sources organized, surfaces gaps, prepares questions and turns scattered inputs into working drafts.

Consultant judgement

The consultant explains the situation, corrects the reading, chooses what matters and decides what can be relied on.

Working memory

The local case folder keeps materials, voice notes, judgement calls, open questions and drafts together across sessions.

How to work with Clara

Use ordinary Codex requests. Clara handles the case folder and reports what changed.

Open or create the case Codex creates or reads the durable local case files."Use Clara on this case folder."
Add materials Documents stay where they are; the plugin registers paths, type, summary and status."Index these documents in the case."
Add notes or transcripts Pasted notes and transcripts become source material in the local case folder."Add these notes to the case."
Use voice capture Codex launches the authorized voice session and imports the downloaded JSON file back into the case."Start a voice recording for this case."
Choose what is ready to use Unreviewed entries can be corrected, held back or moved into the working draft."Show me what is ready to use."
Prepare support material If another person should help with delivery, Clara creates a clean local package without hidden runtime folders."Prepare a support package for review."

When speaking is easier

Voice is a way to capture a debrief without turning the conversation into a form. The imported file returns to the same local case.

Step What happens Result
Launch from Codex The user asks Codex to start voice capture for the active case. The plugin opens the hosted voice screen with a short-lived launch token.
Authorized voice session The hosted server creates the realtime voice session for authorized users. The user does not manage a local API key for voice.
Debrief and sparse follow-ups The voice model listens and asks only sparse follow-ups when useful. The session captures reasoning, caveats and open questions without treating the recording as final advice.
Local JSON file The browser downloads a JSON file at the end of the session. The server is not the case archive; the JSON file is imported locally.
Local import and review Codex imports the downloaded JSON file into the Clara workspace. Transcript is source material. Extracted entries stay separate until they are reviewed.
Important. Directly opening the voice URL is not the normal workflow. The useful session is launched from Clara, then the downloaded JSON file is imported into the local case.

The case persists across sessions

The case folder is the source of truth. A later Codex session can reopen the same folder and continue from the existing files instead of relying on chat history.

File or folder Content
case_manifest.jsonClient, project, objective, audience, language and case status.
case_brief.mdDerived working brief for resuming the case; the JSON files remain the source of truth.
material_registry.jsonIndexed source materials with path, type, summary and status.
judgement_log.jsonFacts, working judgement, Codex inferences and decision implications with inclusion status.
open_questions.jsonTargeted unresolved questions and why they matter.
voice_sessions/Imported voice transcripts and extracted candidates.
exchange_exports/ZIP updates created for another local workspace.
exchange_imports/Local files received from imported update packages.
exchange_log.jsonRecord of imported case-update packages.

Support without a shared folder

Clara is designed for one consultant owning the live case. If delivery support is useful, the consultant asks in normal language and Clara prepares a clean local package. The helper receives context; the local case remains the source of truth.

Delivery support

Ask, package, send, continue.

  • The consultant says what output, issue or draft needs help.
  • Clara packages the case state, relevant working artifacts and a short support note.
  • Hidden OCR/runtime folders, caches and local dependencies are excluded.
  • Returned material can be added back into the local case when it is useful.
  • The consultant does not need to use CLI commands or handle JSON files.

What Clara can prepare

Working briefs, source registers, open-question lists and reviewed drafts are meant to be read before they are shared.

Output package

A traceable working output, not a loose chat summary.

  • case_manifest.json
  • case_brief.md
  • material_registry.json
  • judgement_log.json
  • open_questions.json
  • voice_sessions/
  • case_support_exports/
  • support_request.md
  • exchange_log.json
  • decision_pack.md
  • decision_pack.docx

Review before sharing

Unreviewed judgement is not silently promoted into final drafts. Clara keeps the boundary visible.

Install from Plugin Pack

One ZIP installs all Mparanza plugins except Pro reporting engines. Clara is included; Reporting remains the Pro-only link.

  • Download the Plugin Pack ZIP.
  • Extract it into a stable local folder, for example Documents/CodexPlugins.
  • Open Codex, go to Plugins and choose Add marketplace.
  • Select the extracted Mparanza marketplace folder and install Clara.
  • Open a Codex chat in the project folder and ask Clara to start there.

"Use Clara on this case folder."

Download ZIP