GoWork — Getting started
Install GoWork, connect your models and coding CLIs, and put its resident assistant to work.
Documentation
Product manuals are generated as fast, searchable static pages — easy to read today and easy to migrate into a docs platform later.
Install GoWork, connect your models and coding CLIs, and put its resident assistant to work.
Install OmniPost, connect platform accounts, and publish prepared content from the app or an agent.
How GoWork works — a resident assistant on top of a local model gateway, everything running on your own machine.
How OmniPost works — one publishing core, four interfaces, draft/publish/schedule, isolated accounts, and honest results.
What GoWork's resident assistant can do — run tasks, use tools, remember, automate, delegate, and reach you over IM.
The platforms OmniPost can publish to, grouped by type, with how each one runs and how far automatic publishing is verified.
One local endpoint that fronts your models and coding CLIs — with account pooling, key management, model mapping, and usage tracking.
The three publishing modes, how a post is checked before it goes out, the result codes you get back, plus groups and safety policy.
Reach the GoWork assistant over IM — DingTalk, Feishu, Telegram (WeChat experimental) — and keep tasks running from your phone.
Connect Claude Code, Codex, or your own code to OmniPost over MCP, CLI, or HTTP — and let an agent publish for you.
The MCP tools, CLI commands, and key HTTP endpoints OmniPost exposes.
Where GoWork stores data, the local port, account commands, and environment variables.