The agent-era product line
OmniGoAI builds practical, desktop-first tools for teams putting AI agents to real work. GoWork runs your models and coding agents on one local control plane; OmniPost turns prepared content into safe, repeatable multi-platform distribution.
GoWork and OmniPost are in early access — pricing and downloads are being finalized.
Products
Two local-first tools that share one philosophy — agent-neutral, desktop-first, local by default. Use them together, or on their own. More products are on the way.
The distribution layer for agent-driven content.
OmniPost is an agent-neutral desktop publishing layer. It turns an existing title and Markdown body into drafts, published posts, schedules, and traceable records across many platforms.
A resident AI assistant that gets real work done on your own machine.
GoWork is a local-first AI workbench built around a resident assistant: an LLM-driven agent that understands a task and works through it step by step with real tools — reading and writing files, running commands, searching the web, generating images — or delegates the coding to Codex and Claude Code. It keeps long-term memory, runs scheduled jobs, and reaches you over IM. Underneath sits a unified model gateway that fronts your coding CLIs and API clients.
Workflow
AI agents can write and reason. Running them safely — one gateway in front of every model, and a controlled path from a draft to a published post — is a different problem: sessions, keys, records, scheduling, and a clean manual handoff when automation should stop.
A resident assistant plus a unified localhost endpoint front your models and coding CLIs, with account pooling, memory, and usage tracking.
One publishing core, four interfaces — MCP, CLI, HTTP, and a desktop UI — turn prepared content into drafts, posts, and schedules.
Credentials, sessions, and traceable records stay on your machine, with clear failure reasons and a manual handoff whenever you want one.
Why OmniGoAI
Every product exposes MCP, CLI, HTTP, and a desktop UI on top of a single core — call it however your stack works.
Credentials, sessions, and records live on your machine under ~/.gowork and ~/.omnipost. Cloud is an option, never a requirement.
Genuine Electron browser contexts and local services with isolated account partitions — not fragile extensions or opaque SaaS.
Adapters, skills, and MCP servers let each product grow while its core stays stable.
Product
OmniPost adapters already cover developer communities, Chinese media platforms, social and video surfaces, and overseas API-based publishing targets.
Journal
Field notes, comparisons, and implementation guides — written for operators, not for keyword stuffing.
GoWork's resident assistant runs real tasks on your own machine — using tools, remembering, automating, and delegating to Codex and Claude Code. It is more than a chatbot.
ReadA practical view of why content generation and content distribution should be separate systems — and what the distribution layer should actually own.
ReadFAQ
Two local-first tools. GoWork is a local AI workbench and a unified gateway that fronts your models and coding CLIs. OmniPost is an agent-neutral layer that distributes prepared content across 30+ platforms. More products are planned.
Through the same four interfaces on one core — an MCP server, a CLI, an HTTP API, or a desktop UI. Most agent stacks connect over MCP or HTTP.
Both products are desktop-first and local by default. Credentials, sessions, and records stay on your machine; calls go directly to each provider or platform.
Start with GoWork for models and agents, OmniPost for distribution — or both. Bring your own pipeline; we handle the parts in between.