メインコンテンツまでスキップ

Agent

The Agent page (genkaku.app/agent) is the online agent's home: connect community accounts, pick image preferences, then drive everything from chat — or let calendar missions run it while you are away.

Tabs: settings and calendar​

The page has two tabs: Task settings (this page: accounts + media) and Mission calendar (scheduled and heartbeat work, below).

Community accounts (X / LinkedIn)​

Connect your own X and LinkedIn accounts under settings. The AI only publishes what you confirm, using your own quotas:

  • Chat chips — above the chat composer: X Post, X Reply, LinkedIn Post, Image. Clicking one fills the input with a skill prompt; it never sends on its own. Unconnected networks land on the Agent page to connect first.
  • Confirm cards — drafts arrive as cards with Send / Edit / Schedule / Discard. Scheduling takes a date and time (at least a minute ahead); scheduled posts are stored server-side and fire even with the browser closed.

Media (image preferences)​

Which cloud image model chat generations use, and at which default ratio:

  • The model list comes from the dashboard (Image External Providers): anything added there appears here with no deploy. Pick one, or leave Automatic for default routing (local GPU workers render first).
  • Ratios follow the selected model — only ratios the model supports are offered (e.g. a 1:1-only model never shows 16:9). Switching models auto-corrects an unsupported stored ratio instead of silently falling back.
  • The same preference feeds three paths: the chat image card, conversational image requests, and mission renders.

Mission calendar​

The calendar lives at genkaku.app/agent/missions: a month grid plus an upcoming agenda. Click a day to create, click a chip to edit.

Missions run server-side. Closing the browser never loses them — only unconfirmed composer drafts are client-side. Each firing is recorded with status and cost; five consecutive failures pause the mission automatically.

Triggers​

  • Once — fire at a date and time (a minute to 90 days out).
  • Repeat — daily, weekdays, weekly (pick days), monthly (1–28), in your browser timezone.
  • Heartbeat — wake every N minutes (min 5) and act only when there is something to do (e.g. checking X mentions).

Opening the dialog shows a dry run: the next three fire times plus the per-fire cost estimate before anything is saved.

Assistants (skills)​

Four built-ins: X Post, LinkedIn Post, Image, X mentions check. Skills are open: SKILL.md files in openClaw-compatible format, and the Missions page has a Skills browser (view) plus upload — drop a community skill file, no deploy needed. (Uploaded skills are documentation for now; the runner executes the six known skills.)

Approval and spend caps​

  • Auto-run — fires and executes (posts publish, images render).
  • Confirm first N (default, N=3) — first runs propose draft cards in chat (Send / Edit / Schedule / Discard); automatic from N+1. Best for breaking in a new mission.
  • Always confirm — every run proposes, never auto-runs.
  • Every mission carries a spend cap (total-credits ceiling, default 200). Social posts cost 0; image renders count platform + provider cost. Over cap pauses the mission. Pending drafts show in the agenda with a jump link to chat.

Chains (multi-step)​

Toggle Chain in the dialog for ordered steps sharing one firing — e.g. check mentions → draft a reply → post it → ledger-credit 10 $GENKAKU to the fan, looping up to 5 fans per round. Steps support {{mentionText}} / {{author}} templating. A confirm-gated publish pauses mid-chain; confirming (or discarding, which skips that fan) resumes it. Two more chain-only skills exist for this: x-reply (drafts with the operator model) and fan-reward (ledger points).

Reference docs (.md)​

Upload knowledge files from your PC in the mission dialog (200KB each, click to attach). They are read server-side into reply drafts — SOP stays in the skill, facts stay in your doc. Never stored anywhere public.

Fan rewards (pre-TGE)​

Rewards are ledger $GENKAKU points in the member's existing G account (withdrawable to their own wallet at TGE). Registered members whose X handle is bound are credited instantly; strangers park as pending until they sign up and bind the handle. No hot-wallet moves, no on-chain sends in this version.

Image billing and persistence​

  • Each render is billed in credits (platform charge plus cloud provider pass-through); the exact breakdown rides the image caption (model · size · credits).
  • Images are never stored server-side — they live in your browser only (survives restarts and navigation; clearing site data loses them). Download to keep: hover any chat image for the download button.