Tenki has three products shipping weekly and zero developer community. This is the operating system that's currently missing entirely: a Discord built per-product and per-agent, weekly office hours, a weekly build-in-public stream that runs Tenki against a live OSS bug, a Champions program, and dabl.club's audience as instant top-of-funnel.
A predictable weekly rhythm with high-bandwidth synchronous touch points and a Discord that contributors actually live in — seeded so it isn't an empty room on launch day.
The seeding angle is the unfair advantage. Most startups spend a year building an audience before a community has anyone to talk to. Tenki starts with dabl.club's 86k developers — cross-pollinated via UTMs into Tenki-owned Discord, benchmarks, and events. The community is warm on day one, and every referral is attributed.
The fastest path to a developer community isn't a cold-start grind; it's pulling in communities that already exist next door. Tenki's wedge — the sandbox for long-running, self-improving agents — is the rallying theme that gives those developers a reason to move.
E2B, Modal, and Daytona developers — strong communities, but built around short-lived sandboxes. The long-running-agent story is the open door: persistent volumes, snapshot/restore, sandbox-first brand, owned-compute price.
The builders around Cursor, Codex, and Claude Code. "If you're not playing well with others, you don't win" — meet them inside their own ecosystems with the #claude-code / #codex channels and reference architectures as the on-ramp.
Find the people who already convene these developers — event organizers, hacker-house operators, accelerator leads, top builders — and give them a reason to bring their crowd over. One multiplier moves a room; DevRel can't.
The play in one line. Run Codex / Claude Code meetups that capture their communities, recruit the organizers and top builders as multipliers, and anchor everything to the rallying theme no incumbent is claiming: the home for long-running, self-improving agents. The adjacent community becomes Tenki's community — seeded on top of dabl.club's 86k.
A fixed weekly drumbeat so the community always knows what's coming — and the build-in-public stream the Tenki JD explicitly asks for is the anchor.
| Day | Event | Audience |
|---|---|---|
| Monday | Newsletter draft sent for review (biweekly) | Subscribers |
| Tuesday 11am PT | Office Hours (Zoom + Discord audio, recorded) | CI owners, agent builders, anyone |
| Wednesday | Community "How I ship with Tenki" post published | Blog + HN/Reddit/X |
| Thursday | YouTube drop: migration or Sandbox walkthrough | CI owners, agent builders |
| Friday 10am PT | Build-in-public stream — run Tenki against a live OSS bug | All · YouTube/X live |
The structure mirrors the wedge: one channel per product (runners, review, sandbox), one per agent harness (Claude Code, Codex), plus showcase and benchmarks. Triaged by DevRel and the OpenClaw agent.
Drop-in GitHub Actions migration help. Pinned: the 2-minute migration guide, the cost calculator, and the comparison-vs-incumbents matrix.
AI PR review setup and tuning. Pinned: the reproducible benchmark harness and the honest precision/recall POV.
Disposable microVMs for AI agents. Pinned: "give your agent root without giving it yours" and the microVM-vs-container explainer.
Claude Code + Tenki Sandbox specific. Pinned reference architecture, repo, and quickstart. Co-marketed with Anthropic.
Codex + Sandbox specific. Pinned reference architecture and quickstart. Co-marketed with OpenAI.
Community wins — migrations, agent setups, bugs caught. Best ones go in the newsletter and on X.
Reproducibility help, open-harness questions, community-contributed head-to-heads. The trust engine's home base.
Private to the current Design Partner cohort. Direct line to founders + DevRel.
Support SLA. #runners, #code-reviewer, and #sandbox are triaged by DevRel plus the OpenClaw agent. Target: median first response <15 min during PT business hours, <2h overnight — fast enough that the Discord becomes the obvious place to ask.
Two synchronous anchors a week. Office hours unblock real users; the build-in-public stream is the credibility engine — and it's a literal Tenki JD requirement.
60-minute open Zoom (recorded, published Wednesday). Three slots per session: 15 min demo, 30 min Q&A, 15 min "bring your repo" 1:1 (sign up in advance). What we cover:
The JD asks for "build in public, running Tenki against a real OSS bug." We make it a standing weekly event: pick a live open-source issue, run Code Reviewer on the PR, spin up a Sandbox to reproduce and fix it, ship the PR with the diff + prompt history attached. Published to YouTube and clipped for X. This is the developer-brand motion — done in the open, every week.
Every session ships as a YouTube video + auto-transcribed blog summary. Searchable archive at tenki.cloud/office-hours.
Tenki isn't open-source, so we substitute the OSS contribution flywheel with a recognized-contributor program — see Programs for the full Tenki-for-Open-Source + Champions + Hackathons design (Initiative 6). Champions get amplified, paid, and given platform access.
Anyone with a merged community example, a published "How I ship with Tenki" post, or sustained help in Discord. Perks: name on the contributors page, swag, Discord role.
Multiple reference architectures or examples, OR a published post, OR a conference talk. Perks: monthly retainer for ongoing contributions, advance access to releases and benchmarks.
Sustained year-long contribution. Perks: larger retainer, invited to roadmap reviews, conference travel covered, early access to new products on the substrate.
How this rolls up. Discord + office hours + the weekly stream + Champions close W3 (no community/brand) and W8 (unknown) directly. The North-Star input is community→pipeline: activated workspaces are the top of the sales funnel, and we track community-to-paid conversion explicitly on the metrics dashboard.
Year-1 output target: 2,500 active community engineers, 8,000 newsletter subscribers, 40+ build-in-public streams shipped, and a Champions cohort of recognized contributors by month 12.