Player profile
OpenHuman
A GPL-3.0 personal AI agent harness with a desktop-first UI, local memory tree, Obsidian-style wiki, integrations, model routing, voice, and optional local AI.
Profile
Where it fits
OpenHuman is an open-source personal AI agent harness from TinyHumans. The public README describes a desktop-first assistant with a mascot UI, local SQLite-backed memory tree, Obsidian-compatible wiki, one-click OAuth integrations, native tools, model routing, voice, and optional Ollama-backed local AI.
It belongs in Open Orchestrators because its operating surface is not only chat. OpenHuman connects to user tools, pulls fresh data into memory on a recurring loop, exposes integrations as typed tools, and gives the agent durable personal context for daily workflows.
The repository is GPL-3.0, Rust-primary, and in early beta. Its public repo and website frame the product around private, simple, human-facing personal agent orchestration.
Builder web analytics
Measure projects built with OpenHuman
OpenHuman gives users a personal agent with memory, integrations, and daily workflow context. Agent Analytics measures the public project surfaces, onboarding paths, docs, and product flows those agents help change.
Instrument the product or web surface OpenHuman helps change. Agent Analytics reads user-facing event data; it is not a replacement for OpenHuman's personal memory, local wiki, integration sync, or voice workflow.
First loop to measure
- a builder uses OpenHuman to research, plan, write, update docs, improve onboarding, or ship a product surface
- the affected website, docs path, app path, or onboarding flow reports visits, sources, CTA clicks, signup, activation, retention, and task-completion events to Agent Analytics
- OpenHuman or a follow-up agent reads the Agent Analytics results after the change reaches users
- the next personal-agent task is chosen from user-facing outcomes, not only remembered context
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including OpenHuman-assisted page, docs path, traffic source, CTA click, signup, activation event, retention signal, or task-completion event. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which OpenHuman-assisted page, docs path, traffic source, CTA click, signup, activation event, retention signal, or task-completion event moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.Related