willamhou · willamhou · May 24, 2026 · May 24, 2026
diff --git a/README.ja-JP.md b/README.ja-JP.md
@@ -40,7 +40,7 @@ repo-aware です。
 
 ## クイックスタート
 
-Homebrew でインストール:
+Homebrew でインストール（macOS x64/arm64 で検証済み）:
 
 ```bash
 brew tap willamhou/deepseekcode

diff --git a/README.md b/README.md
@@ -40,7 +40,7 @@ plain chat wrapper. The default path is terminal-first and repo-aware:
 
 ## Quick Start
 
-Install with Homebrew:
+Install with Homebrew (verified on macOS x64/arm64):
 
 ```bash
 brew tap willamhou/deepseekcode

diff --git a/README.zh-CN.md b/README.zh-CN.md
@@ -36,7 +36,7 @@ DeepSeekCode 的目标不是普通聊天壳，而是更接近 Claude Code CLI /
 
 ## 快速开始
 
-通过 Homebrew 安装：
+通过 Homebrew 安装（已验证 macOS x64/arm64）：
 
 ```bash
 brew tap willamhou/deepseekcode

diff --git a/docs/install.md b/docs/install.md
@@ -4,7 +4,7 @@
 
 ## Homebrew
 
-macOS/Linux 推荐从公开 tap 安装：
+macOS 推荐从公开 tap 安装：
 
 ```bash
 brew tap willamhou/deepseekcode
@@ -15,6 +15,8 @@ deepseek doctor --json
 ```
 
 `v0.1.3` 的 tap 已通过 macOS x64 和 macOS arm64 Homebrew Smoke 验证。
+Linux 用户建议优先使用下面的 release archive 或源码安装路径；`v0.1.3`
+的 Linux x64 和 Linux arm64 release assets 已通过 Release Smoke 验证。
 
 ## 从源码安装
 

diff --git a/docs/launch/README.md b/docs/launch/README.md
@@ -16,7 +16,7 @@ Use this concise public-beta claim:
 
 > DeepSeekCode v0.1.3 is a public-beta, DeepSeek-first code-agent CLI for
 > Linux/macOS. It ships GitHub Release binaries, Linux arm64 support, verified
-> Homebrew install, GHCR image, and release-smoke evidence for the local
+> macOS Homebrew install, GHCR image, and release-smoke evidence for the local
 > terminal coding loop.
 
 ## Links
@@ -56,6 +56,8 @@ Also verify:
 - README Quick Start still points to the latest release.
 - Homebrew install works from a clean macOS machine:
   `brew tap willamhou/deepseekcode && brew install deepseek`.
+- Linux users can find release archive and source-install paths in the README
+  and install guide.
 - `docs/current-status.md` still reflects the latest release evidence.
 - Known caveats are visible: npm is not live, Windows is not the current public
   beta focus, and richer GIF/MP4 launch media can still be added.

diff --git a/docs/launch/chinese-community.md b/docs/launch/chinese-community.md
@@ -6,7 +6,7 @@
 ## 标题
 
 ```text
-我做了一个类似 Claude Code 的 DeepSeek 终端代码 Agent，Linux/macOS 可以直接 brew 安装
+我做了一个类似 Claude Code 的 DeepSeek 终端代码 Agent，macOS 可 brew 安装，Linux 有 release 包
 ```
 
 更克制的版本：
@@ -22,18 +22,22 @@ DeepSeekCode v0.1.3：一个 DeepSeek-first 的终端 code-agent CLI
 
 它是一个 DeepSeek-first 的终端 code agent，目标是做一个更接近 Claude Code / Codex CLI 的本地开发闭环：在终端里看仓库、改文件、跑检查、看 diff，然后继续同一个 session 迭代。
 
-现在 Linux/macOS 已经可以直接试：
+现在 macOS 可以直接用 Homebrew 试：
 
 brew tap willamhou/deepseekcode
 brew install deepseek
+deepseek config init
+printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
 deepseek quickstart
 deepseek
 
+Linux 用户可以走 GitHub Release archive 或源码安装；v0.1.3 的 Linux x64 / Linux arm64 release assets 已经纳入 release-smoke。
+
 这版补齐了几个之前不敢公开推的东西：
 
 - GitHub Release 二进制产物
 - Linux x64 / Linux arm64 / macOS x64 / macOS arm64
-- 已验证的 Homebrew tap
+- 已验证的 macOS Homebrew tap
 - GHCR 镜像
 - release-smoke：从公开 release 下载、校验 sha256、解压并跑最小验证
 - README 里有真实 model-backed 的编辑/测试闭环 demo
@@ -58,9 +62,15 @@ DeepSeekCode v0.1.3 public beta 发了。
 
 一个 DeepSeek-first 的终端 code-agent CLI，面向 Linux/macOS 本地开发闭环：看仓库、改文件、跑命令、看 diff、继续 session。
 
-安装：
+macOS 安装：
 brew tap willamhou/deepseekcode
 brew install deepseek
+deepseek config init
+printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
+deepseek quickstart
+deepseek
+
+Linux 可以用 GitHub Release archive 或源码安装，README 里有命令。
 
 Repo:
 https://github.com/willamhou/DeepSeekCode

diff --git a/docs/launch/demo-script.md b/docs/launch/demo-script.md
@@ -25,13 +25,20 @@ working, not to explain every feature.
 
 ## Command Flow
 
+macOS Homebrew path:
+
 ```bash
 brew tap willamhou/deepseekcode
 brew install deepseek
 deepseek version
+deepseek config init
+printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
 deepseek quickstart
 ```
 
+For a live recording, configure the API key off camera or replace
+`<api-key>` with a redacted placeholder in the final edit.
+
 In a disposable repository:
 
 ```bash
@@ -45,8 +52,10 @@ model-backed SVG in the README and record a shorter install/quickstart clip.
 
 ## What To Emphasize On Screen
 
-- `brew install` works.
+- macOS `brew install` works.
+- Linux users have release archive and source-install paths.
 - `deepseek quickstart` gives first-run confidence.
+- API key setup is explicit before a real model call.
 - The agent reads repo context before editing.
 - File changes are reviewable with `git diff`.
 - Tests or checks run in the same terminal loop.
@@ -61,7 +70,7 @@ Recommended content:
 ```text
 DeepSeekCode
 DeepSeek-first terminal code agent
-Homebrew install | Linux/macOS | Public beta
+macOS Homebrew | Linux release assets | Public beta
 ```
 
 Recommended dimensions:

diff --git a/docs/launch/hacker-news.md b/docs/launch/hacker-news.md
@@ -37,17 +37,23 @@ inspect a repo, edit files, run checks, review the diff, and keep working from
 the same terminal.
 
 The current public beta is focused on Linux/macOS. v0.1.3 has GitHub Release
-binaries, Linux x64/arm64 and macOS x64/arm64 assets, a verified Homebrew tap,
-a GHCR image, and release-smoke checks that download and validate the public
-release assets.
+binaries, Linux x64/arm64 and macOS x64/arm64 assets, a verified macOS
+Homebrew tap, a GHCR image, and release-smoke checks that download and validate
+the public release assets.
 
-Quick try:
+Quick try on macOS:
 
 brew tap willamhou/deepseekcode
 brew install deepseek
+deepseek config init
+printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
 deepseek quickstart
 deepseek
 
+Linux users can use the release archives or source install path from the
+README; Linux x64 and Linux arm64 release assets are part of the v0.1.3 smoke
+coverage.
+
 What works today: full-screen TUI, REPL, one-shot run mode, repo-aware file
 tools, shell workflows with approvals, sessions/runtime state, MCP/ACP surfaces,
 rollback/diff review paths, and model-backed demo evidence in the README.
@@ -68,5 +74,7 @@ and where DeepSeek-backed workflows feel different in practice.
 - Do not ask for upvotes.
 - If someone asks about npm, say it is prepared but not published yet because
   the registry token is not configured.
+- If someone asks about Linuxbrew, say the release assets are smoke-tested on
+  Linux x64/arm64, while Homebrew smoke currently covers macOS x64/arm64.
 - If someone asks about Windows, say release assets exist, but Linux/macOS local
   CLI dogfooding is the current milestone.
diff --git a/docs/launch/product-hunt.md b/docs/launch/product-hunt.md
@@ -10,7 +10,7 @@ launch media is still mostly SVG-based.
 Go when:
 
 - npm is either published or the page clearly says Homebrew is the primary
-  install path.
+  macOS install path and Linux uses release archives or source install.
 - A 30-60 second demo video exists.
 - At least three clean screenshots or gallery images exist.
 - README, install docs, and current status match the latest release.
@@ -50,14 +50,14 @@ I built DeepSeekCode because I wanted a terminal-first code-agent workflow for D
 
 The current public beta focuses on Linux/macOS local repo work: inspect a repository, edit files, run commands, review diffs, and continue from the same terminal session.
 
-v0.1.3 includes GitHub Release binaries, Linux arm64 support, a verified Homebrew tap, GHCR publishing, release-smoke checks, and model-backed demo evidence in the README.
+v0.1.3 includes GitHub Release binaries, Linux arm64 support, a verified macOS Homebrew tap, GHCR publishing, release-smoke checks, and model-backed demo evidence in the README.
 
 It is still early. npm publishing is not live yet, Windows is not the current public-beta focus, and I am looking for feedback from people who already use terminal-first coding agents.
 ```
 
 ## Gallery Ideas
 
-1. Homebrew install and quickstart.
+1. macOS Homebrew install and quickstart.
 2. Full-screen TUI in a local repo.
 3. Agent proposing a file change.
 4. `git diff` after the agent edit.

diff --git a/docs/launch/social-posts.md b/docs/launch/social-posts.md
@@ -5,7 +5,7 @@ Use these for X, LinkedIn, Bluesky, Discord, Slack, or project update channels.
 ## One-Liner
 
 ```text
-DeepSeekCode v0.1.3 is a public-beta, DeepSeek-first terminal code agent for Linux/macOS: Homebrew install, release binaries, GHCR, Linux arm64, and release-smoke evidence.
+DeepSeekCode v0.1.3 is a public-beta, DeepSeek-first terminal code agent for Linux/macOS: macOS Homebrew install, Linux release binaries, GHCR, Linux arm64, and release-smoke evidence.
 ```
 
 ## X Thread
@@ -15,16 +15,20 @@ DeepSeekCode v0.1.3 public beta is out.
 
 It is a DeepSeek-first terminal code agent for local repository work: inspect files, edit code, run checks, review diffs, and keep the session in one terminal.
 
-Install:
+macOS install:
 brew tap willamhou/deepseekcode
 brew install deepseek
+deepseek config init
+printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
 deepseek quickstart
 deepseek
 
+Linux users can use the release archive or source install path in the README.
+
 This release includes:
 - Linux x64 + Linux arm64
 - macOS x64 + macOS arm64
-- verified Homebrew tap
+- verified macOS Homebrew tap
 - GitHub Release binaries
 - GHCR image
 - release-smoke checks against public assets
@@ -49,15 +53,19 @@ I released DeepSeekCode v0.1.3 as a public beta.
 
 DeepSeekCode is a DeepSeek-first terminal code agent for local repository work. It is built around a terminal-first loop: inspect a repo, edit files, run checks, review diffs, and continue from the same local session.
 
-The v0.1.3 release now has public GitHub Release binaries, Linux x64/arm64 and macOS x64/arm64 assets, a verified Homebrew tap, GHCR image publishing, and release-smoke checks against the published artifacts.
+The v0.1.3 release now has public GitHub Release binaries, Linux x64/arm64 and macOS x64/arm64 assets, a verified macOS Homebrew tap, GHCR image publishing, and release-smoke checks against the published artifacts.
 
-Install:
+macOS install:
 
 brew tap willamhou/deepseekcode
 brew install deepseek
+deepseek config init
+printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
 deepseek quickstart
 deepseek
 
+Linux users can use the release archive or source install path documented in the README.
+
 This is still a public beta. npm publishing is not live yet, Windows is not the current focus, and I want more real-world feedback from Linux/macOS terminal workflows.
 
 Repo:
@@ -69,12 +77,16 @@ https://github.com/willamhou/DeepSeekCode
 ```text
 I am dogfooding DeepSeekCode v0.1.3, a DeepSeek-first terminal code agent for Linux/macOS.
 
-Install:
+macOS install:
 brew tap willamhou/deepseekcode
 brew install deepseek
+deepseek config init
+printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
 deepseek quickstart
 deepseek
 
+Linux: use the release archive or source install path in the README.
+
 Repo: https://github.com/willamhou/DeepSeekCode
 
 Feedback I am looking for: install friction, first-run UX, approval flow, shell behavior, and whether the terminal coding loop feels useful on real repos.