Skip to content

public-beta.md

Latest commit

 

History

History
169 lines (130 loc) · 5.85 KB

public-beta.md

File metadata and controls

169 lines (130 loc) · 5.85 KB

Public Beta Guide

This guide keeps public messaging aligned with what DeepSeekCode can prove today.

Positioning

DeepSeekCode is a DeepSeek-first terminal code agent for Linux/macOS local development. It is useful when someone wants a repo-aware CLI that can inspect code, edit files, run commands, review diffs, resume sessions, and keep runtime state locally.

The honest public-beta claim is:

DeepSeekCode is usable today for Linux/macOS dogfooding and repository work, with a full-screen TUI, REPL, durable runtime, permissioned tools, shell/PTY workflows, release binaries, a verified Homebrew tap, verified npm/npx install paths, a model-backed README demo set, online dogfood evidence, and first-run checks. Broader external samples and hosted product evidence are still in progress.

Do not describe the project as fully equivalent to Claude Code CLI or Codex CLI yet. The local loop is close enough to dogfood, but the public install and evidence story is still being hardened.

Who Should Try It

Good public-beta users:

  • developers on Linux or macOS who are comfortable with a terminal-first code agent;
  • users who can provide DEEPSEEK_API_KEY;
  • contributors willing to report install, TUI, shell, and repo-editing issues;
  • people evaluating DeepSeek-backed coding workflows rather than hosted IDE integrations.

Less ideal users for this phase:

  • users who need polished hosted IDE flows;
  • Windows-only users who expect service-level parity with Linux/macOS.

First-Run Path

Recommended path for public-beta testers:

npm install -g @deepseek-code/cli
deepseek quickstart
deepseek config init
printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
deepseek doctor --json
deepseek

Homebrew remains available for macOS/Linux users:

brew tap willamhou/deepseekcode
brew install deepseek
deepseek quickstart
deepseek config init
printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
deepseek doctor --json
deepseek

Source install remains available for users who want to build from git:

cargo install --git https://github.com/willamhou/DeepSeekCode.git --locked
deepseek quickstart
deepseek config init
printf '%s\n' '<api-key>' | deepseek config auth DEEPSEEK_API_KEY --stdin
deepseek doctor --json
deepseek

For release archive users, start with:

deepseek update download-plan --version 0.1.6
deepseek update release-smoke --version 0.1.6 --json

Then try a bounded task in an existing repository:

deepseek run "summarize this repository and identify the main test command"

What To Show

The strongest current proof points are:

  • the README 2048 demo pair: a real interactive deepseek chat recording of DeepSeekCode writing the app, plus GIF/MP4 browser gameplay from the same generated repo;
  • supplemental TUI and model-backed edit/test SVGs in docs/demo/;
  • deepseek quickstart and deepseek doctor --json for first-run readiness;
  • CI-smoked TUI entrypoints and service/shell fixtures;
  • deepseek update release-smoke --version 0.1.6 --json for release binary verification on the current platform;
  • npm install -g @deepseek-code/cli and npx @deepseek-code/cli as verified Node-oriented install paths for v0.1.6;
  • verified Homebrew tap install on macOS x64 and macOS arm64;
  • online Python, Rust, and Node external fixture evidence recorded through dogfood tooling;
  • reusable Python, Rust, and Node external fixture scaffolds for refreshing or extending model-backed evidence when needed.

Use docs/current-status.md for the exact state and docs/dogfood-evidence.md for evidence commands.

Public Caveats

Keep these caveats visible when promoting the project:

  • Keep an npm install/npx smoke in release preflight after any packaging or workflow change.
  • Homebrew is published and verified for v0.1.6; keep Homebrew Smoke in the release checklist after every tap formula refresh.
  • More online model-backed runs against larger external fixtures would make the evidence base stronger.
  • Hosted IDE evidence and broader Windows service proof are outside the current Linux/macOS local CLI milestone.
  • The committed interactive 2048 terminal SVG and gameplay GIF/MP4 should still be reviewed in context before each major push, especially if README positioning or release copy changes.

Promotion Checklist

Before a broader public push:

cargo fmt --check
cargo test --lib -- --test-threads=1
node scripts/check-secrets.js
deepseek quickstart --json
deepseek update publish-status --json
deepseek update release-smoke --version 0.1.6 --json

Also check:

Short Copy

Short project description:

DeepSeekCode is a DeepSeek-first terminal code agent for Linux/macOS. It gives you a full-screen TUI, REPL, repo-aware tools, permissioned shell workflows, durable local runtime state, and release evidence for real code editing loops.

Longer public-beta copy:

DeepSeekCode is a public-beta terminal code agent built around DeepSeek and local repository work. It can inspect files, apply patches, run checks, review diffs, resume sessions, and drive shell workflows from the terminal. The Linux/macOS local CLI loop is ready for dogfooding, npm/Homebrew/release archive installs are the public distribution paths, and README launch media now includes a model-backed 2048 demo; broader external repo samples and hosted IDE evidence are still being hardened.