Repository navigation
v9.2.0
Seed Code CLI
Version: 9.2.0
License: PolyForm Noncommercial License 1.0.0
(https://polyformproject.org/licenses/noncommercial/1.0.0/)
WHAT'S IN THIS RELEASE
The v9.2.0 release artifacts:
- Windows portable executable (x64)
- Windows Setup installer (x64)
- Python wheel (any OS)
- Python sdist (any OS)
- npm package tarball (launcher)
- SHA256SUMS.txt checksum file covering all of the above
Primary command after any install method: seedcode
Developer fallback: python -m seedcode
WHAT CHANGED IN v9.2.0
v9.2.0 is the dedicated coding-agent release. It removes the remaining
non-coding features and makes the terminal experience a real, live view of the
agent's work.
-
One unified coding agent. Chat Mode, Agent Mode, Assist Mode and Code Mode
are gone; every request is one agent turn. The deterministic, model-free
intent classifier decides which capability the request needs, so a question
never reads your project and a coding task never fetches the web unless it
must. /chat, /agent, /mode, /assist and /codemode no longer exist. -
Clean live activity log. The repeated "AI >" prefix is gone from agent
activity. Lines are indented under your turn and marked by real state:
a gear for a tool or file operation, a check for success, a cross for
failure and an info glyph for informational events. "You >" is unchanged. -
The spinner shows the actual operation. Instead of a generic "Working...",
the animated spinner carries the backend's current operation - "Reading
README.md...", "Running python -m pytest...", "Waiting for the model
response..." - with a live elapsed timer. -
Real terminal reporting. A completed command reports its real exit code
("Command completed - Exit code: 0"); failed commands report failure. No
operation is ever reported as successful unless it succeeded. -
Real file-operation diffs. Created, updated and deleted files report the
path, line counts, the affected line range and a bounded unified diff. -
Duplicate-free events. One operation produces one activity line: a file
change is rendered by the diff view instead of being printed twice. -
Compact header. The oversized boxed ASCII logo in the fixed header was
replaced by a compact two-row bar: branding/provider/model/mode above,
live status/workspace/context/key below. No line exceeds the terminalwidth at any size and the branding line never churns while the agent
works. -
Removed non-coding features. Desktop control (windows, keyboard, mouse),
OCR/vision, the Computer Engine and the YouTube Music command were removed,
together with their [desktop], [vision] and [browser] extras. The tool
surface is now the coding agent's own: filesystem, search, terminal, git and
web research. -
Workspace lifecycle fix. The engine's permission manager is now bound to
the selected workspace at construction (the missing import that made a
normal message crash with NameError: name 'active_workspace' is not defined
is fixed), and a clean shutdown clears any in-flight initialization state. -
Provider honesty. A failed request is reported, never silently rerouted to
another provider; automatic failover is opt-in (auto_failover) and Ollama
failures surface as Ollama errors. -
Release gate. The build pipeline runs the full test suite before packaging
and refuses to build an artifact when a test fails.
INSTALLATION METHODS
-
Windows - remote PowerShell installer (recommended on Windows)
irm https://seedcode-cli.vercel.app/install.ps1 | iex
Downloads the official SeedCode-CLI-9.2.0-windows-x64.exe from GitHub
Releases and verifies its SHA-256 against the release's SHA256SUMS.txt. A
mismatch, a missing entry, or an unreachable checksum file aborts;
verification is never bypassed. It installs per-user to
%LOCALAPPDATA%\Programs\SeedCode, adds that directory to the user PATH, and
verifies the installed binary reports version 9.2.0. PowerShell 5.1 and 7+
compatible; ANSI UI with graceful fallback; Ctrl+C safe. -
Windows - Setup installer
Download SeedCode-CLI-Setup-9.2.0.exe from
https://github.com/Alshahriar-07/seedcode-cli/releases/tag/v9.2.0 and run it.
Installs with a Start Menu shortcut and adds the install directory to the
PATH soseedcodeworks in new terminals. Preserves configuration during
upgrades (user config lives in the Seed Code config directory, not the
install directory). -
Windows - portable executable
Download SeedCode-CLI-9.2.0-windows-x64.exe from the releases page and
run it directly. No installation, no PATH changes;seedcode --version
reports 9.2.0. For a persistentseedcodecommand, use method 1 or 2. -
Linux / macOS - remote shell installer
curl -fsSL https://seedcode-cli.vercel.app/install.sh | bash
Downloads the official SeedCode-CLI-9.2.0-- standalone binary
from GitHub Releases when the release publishes one for this platform, and
otherwise downloads the official seedcode_cli-9.2.0-py3-none-any.whl. Either
way the downloaded file's SHA-256 is verified against the release's
SHA256SUMS.txt before anything is installed (a mismatch aborts, and an
unreachable checksum file aborts too - verification is never bypassed).
Installs to ~/.local/bin and verifies the installed binary reports 9.2.0.
pipx is used for the wheel when available (otherwise pip --user, with
PEP 668 handling). Clean ANSI UI with ASCII fallback; Ctrl+C safe. -
Any OS - pip
pip install seedcode-cli
Then run:
seedcode (primary command)
python -m seedcode (developer fallback)First launch initializes the per-user configuration in the Seed Code
config directory (never inside site-packages) and prompts for a provider
and model. The wheel requires Python 3.10+.
UPGRADE SAFETY
Upgrades preserve user configuration and provider/API settings. The Windows
installers upgrade in place; configuration lives in the Seed Code config
directory and is never deleted by an installer.
CHECKSUMS
Every release artifact has a SHA-256 entry in SHA256SUMS.txt:
cd dist/release/9.2.0
sha256sum -c SHA256SUMS.txt # Linux/macOS
Get-FileHash -Algorithm SHA256 # Windows
Both remote installers verify before installing: they read the release's
SHA256SUMS.txt as the authoritative expected value and abort on any mismatch
or a missing entry. If the checksum file is unreachable, the install aborts
rather than proceeding unverified - verification is never bypassed. All
digests are computed from the final published artifacts; none are invented.
SUPPORT
Releases: https://github.com/Alshahriar-07/seedcode-cli/releases
Issues: https://github.com/Alshahriar-07/seedcode-cli/issues
Docs: https://seedcode-cli.vercel.app