First commit of the Next.js community site that powers deepseek-tui.com, deployed via Cloudflare Workers / OpenNext. This commit lands the scaffold and applies the visual + correctness pass requested by community feedback: - Palette: drop the cream/Anthropic-feel paper (#F4F1E8) for a DeepSeek-aligned cool white + soft gray (#FFFFFF / #F4F6FB), with indigo accents kept. Soften default hairlines so a pure-white background reads clean instead of harsh. - Mobile: add a hamburger menu (mobile-menu.tsx) so phones can reach Install / Docs / Activity / Roadmap / Contribute — previously the link list was hidden on phones with no replacement. Tighter hero, flexible button row, viewport-safe code blocks, columnar grids collapse cleanly under 768px, and the printed-almanac center rule is desktop-only now (it sliced through narrow viewports). - "How it works" diagram: replace the hand-rolled ASCII art (which misaligned under CJK monospace because Han characters take 2 columns vs Latin's 1, per dhh's note in WeChat) with a real mermaid diagram rendered client-side via dynamic import. Uses the mermaid.live standard syntax 庄表伟 recommended. - Issue #1104: the docs listed a `deepseek-cn` provider that the v0.8.16 binary doesn't accept (`ProviderArg` in crates/cli only has 9 variants; the 10th lives only in the legacy tui/config.rs). derive-facts.mjs now omits `deepseek-cn` until that variant is wired through the shared ProviderKind, and the install page's China-network recipe uses `base_url` / `DEEPSEEK_BASE_URL` (which actually works on v0.8.16) instead of the unsupported provider. Auto-deploys via .github/workflows/deploy-web.yml on push to main. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4.7 KiB
Community Assistant Agent
The community assistant is a set of Cloudflare Cron Triggers that call deepseek-v4-flash to draft triage comments, PR reviews, stale-issue nudges, duplicate suggestions, and weekly digests. It never posts to GitHub directly. Every output is a draft staged in Workers KV for maintainer review.
Architecture
Cloudflare Cron Triggers
└─ worker.ts scheduled() handler
├─ */30 min → triage (new issues) + pr-review (new PRs)
├─ daily → stale (30d inactive) + dupes (embed-similarity scan)
├─ weekly → digest (Mon 09:00 UTC)
└─ 6h → curate (Today's Dispatch — pre-existing)
Drafts stored in Workers KV:
draft:triage:<issue-number>
draft:pr-review:<pr-number>
draft:stale:<issue-number>
draft:dupes:<issue-number>
draft:digest:<year>-W<week>
Usage logged to:
usage:<YYYY-MM-DD>
Cron schedule
| Expression | Frequency | Tasks |
|---|---|---|
0 */6 * * * |
Every 6 hours | Today's Dispatch (curate) |
*/30 * * * * |
Every 30 min | Issue triage + PR review |
0 0 * * * |
Daily 00:00 UTC | Stale issue nudges + duplicate detection |
0 9 * * 1 |
Monday 09:00 UTC | Weekly digest |
Voice constraints
All drafts follow these rules:
- Calm, factual, never breathless.
- Never uses first person plural ("we"/"我们") — the maintainer is one person.
- Never commits to timing, prioritisation, or merge intent.
- Never apologises on the maintainer's behalf.
- Cites specific files / line numbers / linked issues when discussing code.
- Ends with: "— drafted by community assistant, pending maintainer review"
- Chinese drafts end with: "— 由社区助理草拟,待维护者审阅"
- Chinese output is rewritten in zh-CN, not machine-translated.
Cost guardrails
- Each cron invocation caps at ~30k input tokens and ~2k output tokens.
- Issue/PR bodies are truncated to 1000–4000 chars before sending to the model.
- Deduplication:
hasFreshDraftchecks if a draft already exists that's newer than the item'supdated_at. Skips if so. - Token usage is logged to
usage:<YYYY-MM-DD>KV keys (retained 90 days). - If
DEEPSEEK_API_KEYis missing or the API errors, the cron returns 200 with{ skipped: true, reason }— never crashes, never retry-loops.
Maintainer review surface
Access at /admin?token=<MAINTAINER_TOKEN>.
- Lists all pending drafts with source link, draft body, and three actions:
- Post as comment — calls GitHub REST API using
MAINTAINER_GITHUB_PAT - Edit & post — opens a textarea for editing before posting
- Discard — removes the draft from KV
- Post as comment — calls GitHub REST API using
- The auth token is set via
MAINTAINER_TOKENenv var. Access sets anmtcookie for the session. - Nothing posts to GitHub without an explicit maintainer click.
Environment variables
| Variable | Required | Purpose |
|---|---|---|
DEEPSEEK_API_KEY |
Yes | DeepSeek API key for the community agent |
GITHUB_TOKEN |
Optional | Fine-grained PAT for GitHub API (raises rate limit) |
CRON_SECRET |
Optional | Shared secret for manual cron invocation |
MAINTAINER_TOKEN |
Optional | Auth token for /admin panel |
MAINTAINER_GITHUB_PAT |
Optional | GitHub PAT with issues:write scope for posting comments |
Initial deployment
One-time setup before the first npm run deploy:
-
Create the KV namespaces:
npx wrangler kv namespace create CURATED_KV npx wrangler kv namespace create NEXT_INC_CACHE_KVCopy the returned
idvalues and paste them into the matchingwrangler.jsoncbindings, replacing each"REPLACE_WITH_KV_ID". -
Set secrets:
npx wrangler secret put DEEPSEEK_API_KEY npx wrangler secret put MAINTAINER_TOKEN npx wrangler secret put MAINTAINER_GITHUB_PAT npx wrangler secret put CRON_SECRET -
(Optional) Raise GitHub rate limit:
npx wrangler secret put GITHUB_TOKEN -
Verify:
npm run predeploy # checks KV ID is set npm run deploy # builds + deploys
Kill switch
To disable the community agent entirely:
- Remove all cron triggers from
wrangler.jsoncexcept the original0 */6 * * *(curate). - Redeploy:
npm run deploy.
The curate cron (Today's Dispatch) continues working independently. Individual tasks remain callable manually for testing through /api/cron?task=triage, /api/cron?task=pr-review, etc.
To disable a specific cron task, remove its cron expression from wrangler.jsonc and redeploy.
Bilingual output
Every draft contains both bodyEn (English) and bodyZh (Chinese zh-CN). The admin panel shows the version matching the current locale. The zh version is rewritten natively by the model, not translated from English.