Owoji
Request access

How to use Owoji.

Owoji captures work, structures it into reusable workflows, and runs those workflows as agentic systems with artifacts and proof.

macOS 14+ Command Palette Workflows → Agents → Runs

Getting started

When you first open Owoji, complete onboarding and confirm your capture permissions. If capture is blocked, Settings will tell you exactly what is missing.

First run checklist
  1. Open Owoji and complete onboarding.
  2. Go to Settings → System warnings.
  3. Enable Screen Recording if capture is blocked.
  4. Use the top search field to open the Command Palette.
onboarding Step 1
Onboarding flow showing the Owoji welcome screen and a sample workflow preview.

Core concepts

Owoji uses a few objects across the product. You will see these names repeated in the UI and in run results.

Session
A captured work session with events, context, notes, and assets.
Workflow
A structured sequence of steps derived from one or more sessions.
Agent
A reusable template: schema, permissions, checkpoints, and execution rules.
Run
One execution of an Agent with live outputs, logs, timing, and cost.
Artifact
An output from a Run: documents, files, links, metrics, and proof.
Listing
A community entry for a proven workflow, backed by proof runs and outcomes.

Capture a session

Sessions are the raw material. Start capture when you begin real work. Set intent so the system can interpret what matters.

  1. Open Capture from the sidebar.
  2. Set capturing intent to describe the goal of the workflow.
  3. Work normally across your tools while Owoji captures context.
  4. End capture when the workflow completes.
capture sessions Live
Live capture screen showing an event stream, detected structure, and context.

Review the raw timeline

After capture, review the session timeline. Use filters to find important transitions, decisions, and artifacts.

capture review Timeline
Raw session timeline with event details and context.
What to look for
  • Key navigation and decision points
  • Notes and tags you want preserved
  • Artifacts that represent “proof” of the work
  • Context that should be an input for future runs

Structure into a workflow

Structure converts raw events into editable clusters and steps. This is where you decide what is reusable.

session → process Structure
Session to process screen showing raw events mapped into clusters and steps.

Create an agent template

Turn a workflow into a reusable agent: define inputs, outputs, checkpoints, and permissions. Version the template so changes stay comparable across runs.

template editor Schema
Template editor with process steps and input/output schema.

Run and evaluate

Runs are where systems prove themselves. Watch progress, review outputs, and compare results across versions.

live execution Running
Live agent execution with step progress and live outputs.
results Proof
Run results screen with outputs and summary metrics.

Artifacts and versions

Artifacts are the durable outputs of a run. Use versions and lineage to understand how an output was produced and how it changed over time.

artifact viewer Versions
Artifact viewer showing preview, versions, lineage, and metadata.

Deploy and community

Use Deploy to find workflows that already work. Review proof runs, required tools, and outcomes before you unlock or fork.

deploy Explore
Explore screen with featured workflows and filters.
listing detail Proof
Listing detail screen showing proof metrics and actions.

Permissions and settings

Capture relies on macOS permissions. If capture is blocked, open Settings and resolve system warnings first.

settings Permissions
Settings screen showing system warnings and a screen recording permission prompt.

Keyboard shortcuts

Owoji is designed for speed. Use the Command Palette and direct navigation shortcuts to move across the app.

⌘K
Open Command Palette
⌘1
Home
⌘2
Capture
⌘3
Sessions
⌘4
Workflows
⌘5
Agents
⌘6
Runs
⌘7
Deploy
⌘8
Settings
Request access Back to landing