Epic: Publishable, monetizable agents for non-technical creators

[duyet]

Epic: Publishable, monetizable agents for non-technical creators

Turn OMA from a developer/operator platform into one where a non-technical creator can build an agent (e.g. "duyetbot"), publish it to a public URL, let anyone log in and chat, charge money, give it memory + proactive notify-back + hooks, and (infra) let the Cloudflare deployment run sandboxes on k8s.

What already exists (do not rebuild)

Exploration of the current codebase found the platform layer is further along than it looks:

• Multi-tenancy: tenant-centric data model, memberships + roles (owner/admin/member); every signup gets its own tenant (apps/main/src/auth-config.ts → ensureTenant()).
• Auth: better-auth email-OTP for Console; per-tenant/user API keys (packages/http-routes/src/api-keys/).
• Usage metering: per-tenant sandbox/browser seconds in usage_events (packages/db-schema/src/cf-auth/usage.ts), plus quotas (packages/quotas). Billing credits/Stripe are deliberately out-of-tree (hosted worker behind BILLING_INTERNAL_SECRET).
• Console: polished React/Vite admin console with a working chat playground + agent-create-from-template.
• Memory + notify-back: memory stores (R2+D1); notify-dispatch posts to Slack/GitHub/Matrix on session end.
• Scheduler: cron infra (system jobs only).
• Sandbox: a Node-only k8s adapter exists; boxrun proves the "CF Worker drives a remote sandbox over plain fetch" pattern.

Design constraint (from the maintainer)

Multi-tenancy stays on a single shared D1 with row-level tenant_id isolation — no per-tenant shard DBs. Every new table below carries tenant_id and lives in the existing control-plane D1 (env.ROUTER_DB ?? env.MAIN_DB).

The 7 gaps → child issues

Product critical path (dependency order):

• Published agents + public end-user chat surface #72 — Published agents + public end-user chat surface (keystone)
• End-user (consumer) accounts, distinct from tenant owners #73 — End-user (consumer) accounts, distinct from tenant owners (depends on Published agents + public end-user chat surface #72)
• Per-end-user metering + paywall (credits/Stripe) for published agents #74 — Per-end-user metering + paywall (credits/Stripe) (depends on Published agents + public end-user chat surface #72, End-user (consumer) accounts, distinct from tenant owners #73)
• No-code agent builder + one-click publish (Console) #75 — No-code agent builder + one-click publish (depends on Published agents + public end-user chat surface #72; surfaces End-user (consumer) accounts, distinct from tenant owners #73/Per-end-user metering + paywall (credits/Stripe) for published agents #74 settings)

Enhancers (parallelizable once #72 lands):

• Generic outbound webhooks + agent hooks (pre/post-tool, lifecycle) #76 — Generic outbound webhooks + agent hooks (pre/post-tool, lifecycle)
• User-facing scheduled / proactive agent runs #77 — User-facing scheduled / proactive agent runs (uses Generic outbound webhooks + agent hooks (pre/post-tool, lifecycle) #76's webhook target)

Infra track (independent — can start immediately):

• Cloudflare Worker → remote k8s sandbox via HTTP gateway #78 — Cloudflare Worker → remote k8s sandbox via HTTP gateway

Suggested sequencing for a handoff agent

1. Cloudflare Worker → remote k8s sandbox via HTTP gateway #78 in parallel from day one (infra, no product deps).
2. Published agents + public end-user chat surface #72 first on the product track — everything else needs the publication primitive.
3. End-user (consumer) accounts, distinct from tenant owners #73 → Per-end-user metering + paywall (credits/Stripe) for published agents #74 (identity then money), then No-code agent builder + one-click publish (Console) #75 (the UI that ties publish + pricing together).
4. Generic outbound webhooks + agent hooks (pre/post-tool, lifecycle) #76 → User-facing scheduled / proactive agent runs #77 last (proactive/hook polish).

Each child issue is self-contained with concrete file:line seams, the single-D1 constraint, and acceptance criteria, so it can be picked up without re-deriving context.

[coderabbitai]

🔗 Related PRs

#39 - feat(deploy): production prep — strip billing bindings, single-D1 layout, provisioning script [merged]
#105 - docs: rewrite quickstart with Docker/Cloudflare/K8s paths (Issue #95) [open]
#106 - feat: publishable agents integration (webhooks, publications, k8s-remote sandbox) [merged]
#122 - feat(consumer): guest mode, session refresh, and creator end-user visibility (#73) [merged]
#149 - feat(console): setup-steps 'How it fits together' with agent hero [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[duyet]

Status from the 2026-07-17 autonomous run: large parts of this epic shipped — publish flow in Console (#236), hosted /p/ chat (#224), guest→email consumer auth hardened (#213), Stripe checkout credits the live wallet with DB-enforced idempotency (#207), per_1k_tokens metering debits (#206), pricing config route (PUT /v1/publications/:id/pricing). Still open from the epic: subscriptions mode enforcement, creator revenue UI, edit-publication flow (#237), non-technical onboarding polish. Suggest re-scoping this epic to the remainder.

[duyet]

Epic status (autonomous run 2026-07-17): #72, #73, #74, #75, #77, #78 all shipped and closed — checklist updated. Only remaining child: #76, whose webhook half is shipped; the pre/post-tool agent-hooks half is the sole open scope. This epic can close once #76 is resolved or re-scoped.

[duyet]

Progress update: tenant teammate invites shipped (#175 → #277), publication slug uniqueness enforced on all dialects (#268 → #272), anonymous usage telemetry + public stats page shipped (#278/#279/#280), and full token-breakdown tracking with analytics UI (#276).