Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runwita.com/llms.txt

Use this file to discover all available pages before exploring further.

This is the loop Runwita exists for: get content in, let the AI read it, review what came out, save it onto the right journey. The whole thing takes about a minute. Before you start, make sure you’ve completed the prerequisites: an AI provider configured, and at least one way to get content into the Inbox.

​
What counts as an engagement

Anything text-based that captures what was discussed. Runwita accepts:
  • A transcript from any recording or transcription tool that exports text.
  • Pasted notes from a conversation you took by hand.
  • An exported .eml email thread.
  • A PDF or Word doc with notes.
  • An image of a whiteboard or a screenshot, processed via OCR on macOS.
For your first run, the cleanest path is a transcript or pasted notes. Email and image flows work the same way but layer extra parsing on top.

​
The Inbox

Everything starts in the Inbox.
The Inbox showing a ready-for-review item with its extracted title and journey match
The Inbox shows new captures at the top, ready-for-review items below. New items are anything that hasn’t been processed yet. Ready items are ones the AI has read and you haven’t filed yet. Three ways to feed it:
  • Drag and drop a .txt, .md, .pdf, .docx, .eml, or image file onto the Inbox.
  • Paste text directly using the Capture box at the top.
  • Folder watch. If you’ve pointed Runwita at a folder in Settings → Connections, any new file dropped in that folder appears here automatically.

​
Process with AI

Click an inbox item to open it. You see the transcript on the left and a column on the right marked Runwita reading.
The Process with AI screen with the engagement date editor visible
Before clicking Process with AI, set:
  • Engagement date. Defaults to the file’s modification date. The AI uses this to resolve relative phrases like “by Friday” in extracted action items. If the date is wrong, the due dates on every action will be wrong. Pick the right date here.
Click Process with AI. Runwita streams the extraction in real time, you’ll see sections, decisions, and actions populate as they come back. Most engagements extract in 10 to 30 seconds. Long merged extractions (multiple transcripts stitched together) can take up to a minute. If you haven’t configured an AI provider yet, this button will fail with a clear error pointing back to Settings. See Prerequisites. When extraction finishes, the panel shows a green ✓ Complete badge and a summary card. Two buttons sit at the bottom:
  • ↺ Reprocess with AI, throws away this extraction and drops you back to the start. Use this if the date was wrong, or you want to try a different model.
  • Review & Save →, takes you to the review screen.

​
Review and Save

The review screen is your last chance to edit before the engagement is created.
Review & Save with the journey picker, engagement date editor, and the extracted brief
Three things to confirm:
1

Journey

Runwita auto-suggests a journey based on the engagement content. You’ll see one of:
  • High confidence, the AI is sure. Already selected.
  • Medium confidence, plausible match. Already selected, but worth a glance.
  • Low / no match, you’ll need to pick or create one.
Click Change to pick a different existing journey, or + New to create a fresh one inline.
2

Engagement date

The AI’s best guess at the date, prefilled. Override here if it’s wrong. Whatever’s in this field at save time becomes the engagement’s date on the journey timeline.
3

The extracted brief

Title, summary, sections, decisions, actions, attendees. Everything is editable inline. Hover any line to see which part of the source it came from in the right pane.
When everything looks right, click Save to journey →. Runwita does three things in one go:
  1. Creates the engagement on the journey.
  2. Runs topic matching, deciding whether each section maps to an existing topic on the journey or creates a new one.
  3. Pushes any TickTick-flagged actions to TickTick (if connected).
You’re back at the journey, with the new engagement at the top.
Journey page with the newly-saved engagement at the top of the timeline

​
What just happened

In the database, Runwita just did all of this:
  • Created an engagement row linked to the journey.
  • Stored sections, decisions, actions, attendees as related rows.
  • For each AI-detected topic, either created a new topic or attached a touchpoint to an existing one.
  • Marked the inbox item as processed.
The journey page now shows this engagement in its history, and the topics list (left rail on the journey) reflects whatever was discussed.

​
What’s next

Concepts: journeys

The deeper logic behind journeys, why they’re shaped the way they are.

Concepts: topics

How threads of discussion span engagements.