What is OWOJI now?
OWOJI is an autonomous agent engine: Goal → Agents Run → Outputs Ship → Templates Compound. The macOS app remains the command center and observer.
Resources
Practical docs for using OWOJI, a product of OWO INNOVATIONS LLC, from autonomous goals and agent output templates to capture, log editing, packaging, export, billing, macOS permissions, and the Skill Engine for reusable agent instructions.
Frequently asked questions
What does /goal do?
A /goal creates a guarded agent run with budget caps, provider allowlists, audit events, tasks, outputs, and remixable templates.
What can agents produce?
Skills, web pages/components, scripts, launch content, business/research docs, brand systems, motion briefs, CAD/product briefs, and reusable templates.
Can I pause autonomous runs?
Yes. The backend includes a workspace kill switch through /agents/pause and /agents/resume so autonomous work can be stopped without deleting data.
How do I start as a new user?
Download the macOS app, launch OWOJI, complete onboarding, then create or sign into your workspace.
How does capture work?
Open Capture, title the session, describe the workflow goal, grant permissions, then press Start Capture.
Can I add details that were missed?
Yes. The capture screen includes a bottom note box that appends your note as a manual detail event in the live log.
How do I edit my log?
After stopping capture, the Log screen lets you remove noise, mark variables, mask sensitive actions, and add review notes.
What is packaging?
Packaging is a Pro feature. It turns a condensed capture timeline into a structured workflow with title, summary, steps, tools, risks, and handoff files.
What can I export?
Free workspaces can export raw Markdown and raw JSON. Pro workspaces can export the full agent packet ZIP with AI-organized workflow structure.
How does billing work?
The app opens the website pricing page. You sign in or create your workspace there, then secure checkout completes Pro billing.
Does Free use AI?
No. Free captures the session and exports raw logs only. AI summaries, workflow packaging, risk rationale, and agent packet ZIPs require Pro.
Which macOS permissions are required?
Screen Recording and Accessibility are required for real capture. OWOJI checks them before starting a session.
What is the OWOJI Skill Engine?
It is the backend layer that turns captured workflows, docs, repositories, and research into governed skills AI agents can search, call, evaluate, and improve.
How do Skill Builder, Garden, and Finder work?
Builder compiles source material into a skill, Garden stores trusted versions with feedback and lineage, and Finder retrieves the right skill for a task.
Will OWOJI support API, CLI, and MCP access?
The REST API foundation exists first. CLI and MCP distribution are planned so agent runtimes can search and retrieve skills directly.
No results
Guides
Goal engine
Create a goal with a title, category, cadence, and prompt. OWOJI records the run, tasks, outputs, templates, and audit events so the work is observable.
Output gallery
The gallery organizes autonomous outputs by category. Each output is designed to become a template that can be remixed for another use case.
Metrics tracker
The metrics route tracks goals, agent runs, outputs, templates, remixes, sessions, exports, feedback, and estimated time saved for product and investor reporting.
Onboarding
- Open OWOJI and complete the short product orientation.
- Create an account or sign into an existing workspace.
- Land on Home, review usage limits, then open Capture.
Capture
- Name the capture before recording so the session is easy to find later.
- Describe the workflow goal and any packaging notes.
- Grant Screen Recording and Accessibility when prompted.
- Start capture, perform the workflow, then stop when the task is complete.
- OWOJI logs app switches, browser tab changes, focused prompt/input contexts, video-reference moments, and manual notes into one live timeline.
Editing logs
Use the Log screen to remove irrelevant events, mask sensitive details, mark variables, and add notes that explain edge cases.
Adding missed details
During capture, type the missing context into the detail box and save it. OWOJI stores it as a manual note event attached to the session.
Packaging
Pro packaging condenses the capture into a bounded timeline, then creates strict structured JSON with actionable steps, expected outcomes, agent instructions, deployable use cases, acceptance checks, and a handoff prompt. Free users see a paywall before packaging starts.
Exports
- Markdown for readable capture notes.
- JSON for structured session data.
- Agent packet ZIP for Pro handoffs.
Billing
Start Pro checkout from the app or website pricing page. The app redirects to the website, the website creates a secure checkout session, and payment details are handled by a PCI-compliant provider. OWOJI updates entitlements automatically after checkout.
Permissions
OWOJI preflights capture permissions before recording. If either permission is missing, the app shows a permission gate with Grant, Open System Settings, and Refresh actions.
Skill Builder
Skill Builder ingests a workflow, documentation page, repository reference, or browser research trail and compiles it into a reusable agent skill with expected inputs, outputs, risks, and validation checks.
Skill Garden
Skill Garden stores versioned skills with source lineage, tags, feedback, quality scores, and improvement jobs so teams can reuse instructions with confidence.
Skill Finder
Skill Finder searches the garden by domain, tool, task, or use case and returns the best-fit skill for humans, APIs, CLI workflows, or future MCP tools.
How OWOJI Works
Goal → Agents Run → Outputs Ship → Templates Compound.
OWOJI separates command, execution, output, and governance. Goals create agent runs; runs produce outputs; outputs become remixable templates; templates compound into the Skill Garden. The macOS capture app still records human workflows, but the web gallery and autonomous engine now form the primary product surface.
Observe
Start Capture checks permissions, creates a private workspace session, and appends batched app, tab, prompt, video, and note events as you work.
Clean
Use the bottom detail box or inline plus controls to add context that the capture could not infer.
Structure
Pro packaging builds a cached, bounded timeline and returns strict JSON workflow structure.
Export
Free exports raw Markdown/JSON. Pro unlocks the full agent packet ZIP for handoff.
Build
Compile workflows, docs, GitHub references, and web research into strict Markdown skills.
Scale
Store reusable skills with tags, versions, source hashes, and searchable metadata.
Govern
Track invocation history, feedback, risks, ratings, and source lineage for trust.
Optimize
Schedule improvement searches and refresh skills when tools or docs change.
Free vs Pro boundary
Free includes capture, manual details, raw Markdown export, and raw JSON export. It does not summarize sessions, package workflows, create risk rationale, or export agent packets.
Website checkout flow
Upgrade buttons in the macOS app open the website with the selected cadence. Users sign in or create a workspace, then the website redirects to secure checkout for monthly or annual Pro.
Loading states
Capture, billing, packaging, and export surfaces use skeletons or explicit loading overlays so users know the app is working.
Error states
Errors return a clear title, plain-language message, and retry path. Paywall errors point to Upgrade to Pro instead of failing silently.
Rate limits
Server-side limits protect free-tier usage, event ingestion, packaging, and exports from runaway requests.
Cost control
Pro packaging is cached by source hash and uses condensed timelines instead of processing entire raw logs repeatedly.
Manual detail quality
Inline plus controls and the bottom detail box accept text, valid JSON, or inline SVG. PNG references are rejected so exported agent packets stay code-readable.
What a package contains
A Pro package includes workflow title, target, summary, tools, steps, risk level, risk rationale, source session metadata, and export-ready handoff files.
What a skill contains
An OWOJI skill includes purpose, source lineage, prerequisites, steps, expected output, validation checks, risk notes, tags, and feedback metadata.
API, CLI, and MCP path
The current backend exposes REST endpoints for skill ingest, compile, search, garden listing, feedback, and improvement jobs. CLI and MCP surfaces are the distribution layer for agent runtimes.