tmcode v0 = opencode 1.17.4 renamed distribution. Deep rebrand in progress; see README.
tmcode v0 = a renamed repackaging of opencode 1.17.4.
Deep rebrand (source-level rename,
~/.tmcodeconfig-dir isolation, brand strings in CLI output) is in progress and will land in v1. For v0 the binary is opencode 1.17.4 unmodified — the only thing that changes is the npm package name, the bin name, and the install path. The binary will still read and write its config to~/.config/opencode/and~/.local/state/opencode/etc. because that's compiled into the upstream binary.
Source repo: https://github.com/sleep2agi/tmcode
npm install -g tmcode
Then run:
tmcode
Other platforms (darwin-x64, linux-arm64, windows-arm64, glibc-variants) will follow in subsequent releases.
This package is a fork-and-repackage of the opencode project, distributed under its original MIT license. The upstream LICENSE is preserved verbatim. All credit for the actual coding-agent runtime, TUI, language-model integration, and tools goes to the opencode authors and maintainers.
This v0 release exists to give downstream users a stable npm package name (tmcode) and CLI name (tmcode) that they can pin while the v1 deep-rebrand lands.
A full source-level rebrand of opencode's ~25-package monorepo and Go TUI binary (including Apple Silicon cross-compile from a Linux build host) is on the order of 3–5 hours. v0 ships in ~30 minutes as a wrapper-only repackaging so downstream users can begin pinning the name; v1 with the proper source rebuild and config-dir isolation follows.
MIT — same as upstream opencode. See LICENSE.
FAQs
tmcode v1 = opencode 1.17.4 source-rebuilt with renamed config dirs (~/.config/tmcode), bin name 'tmcode', and own brand. Deep rebrand WIP.
The npm package tmcode-ai receives a total of 507 weekly downloads. As such, tmcode-ai popularity was classified as not popular.
We found that tmcode-ai demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
More than 140 Mastra npm packages were compromised in a supply chain attack that used a typosquatted dependency to deliver a cross-platform infostealer during installation.
Research
/Security News
A new npm package tests AI malware scanners with prompt injection, safety-triggering comments, context flooding, and obfuscated JavaScript.
Product
Socket now detects supply chain risks in project manifests, starting with missing lockfiles that can make dependency installs non-reproducible.