Documentation

Documentation.

Product manuals are generated as fast, searchable static pages — easy to read today and easy to migrate into a docs platform later.

Docs

Core concepts

How GoWork works — a resident assistant on top of a local model gateway, everything running on your own machine.

Docs

Core concepts

How OmniPost works — one publishing core, four interfaces, draft/publish/schedule, isolated accounts, and honest results.

Docs

Assistant capabilities

What GoWork's resident assistant can do — run tasks, use tools, remember, automate, delegate, and reach you over IM.

Docs

Supported platforms

The platforms OmniPost can publish to, grouped by type, with how each one runs and how far automatic publishing is verified.

Docs

Model gateway

One local endpoint that fronts your models and coding CLIs — with account pooling, key management, model mapping, and usage tracking.

Docs

Publishing, drafts & scheduling

The three publishing modes, how a post is checked before it goes out, the result codes you get back, plus groups and safety policy.

Docs

Channels

Reach the GoWork assistant over IM — DingTalk, Feishu, Telegram (WeChat experimental) — and keep tasks running from your phone.

Docs

Driving OmniPost from an agent

Connect Claude Code, Codex, or your own code to OmniPost over MCP, CLI, or HTTP — and let an agent publish for you.

Docs

API reference

The MCP tools, CLI commands, and key HTTP endpoints OmniPost exposes.

Docs

Reference

Where GoWork stores data, the local port, account commands, and environment variables.