Temm1e 6.0 — a steadier home for Tem
Released and verified: all six primary binaries, four updater aliases and checksums are published. The v5.8.1 → v6.0.0 update smoke passed on macOS Apple Silicon.
Tem keeps its identity as a persistent companion that uses the model you choose. This release rebuilds important execution boundaries around that idea: provider-native context, scoped conversation storage, model/resource identity, interrupted delivery, evidence and background ownership.
For everyday use
- A compact terminal transcript with expandable tool activity, optional panels, streaming and retained history.
- Explicit Z.ai Coding Plan setup alongside API-key and existing Codex OAuth connections. Account access and subscription quota remain provider-controlled.
- Current model suggestions and native OpenAI Responses, Anthropic and Gemini replay paths; unknown capabilities and usage are represented honestly.
- Source-backed context compaction with raw history retained and scoped recall, rather than silently discarding the only copy of a conversation.
- Saved final replies and commands to inspect interrupted work. A partial or uncertain send is not blindly repeated.
- Goal/check/evidence records that distinguish an answer from a verified result.
- Shared owning usage across foreground and auxiliary calls, bounds on background work and private browser profiles.
- Verified binary updates and guarded developer builds to reduce accumulated disk use.
Upgrade behavior
Back up the entire selected profile before upgrading. Existing legacy chats are preserved; /history-import previews explicit import into an empty scoped conversation. /session-new preserves old evidence; TUI /clear clears the display only.
CLI/server /model <id> now changes the running instance while keeping state and saved startup defaults. The server's model remains instance-wide. TUI has a separate setup/persistence flow. The next inference checks account access; selecting a model does not make a paid validation call.
Automatic copying of personal Chrome sessions is removed. Existing explicit bounded profile import remains available. Finite USD budgets do not interpret unknown subscription prices as free usage.
Validation and limits
Final candidate f9c3e26 passed all 8 CI jobs, including Rust 1.91.1, Linux/Windows, musl/glibc and Docker. Linux 3,138 tests passed (21 ignored); Windows 3,109 passed (20 ignored), reported separately. Local CLI/TUI/persistence/recovery acceptance passed. The tagged source has the same tree as the checked candidate; the tag workflow additionally checks and builds the distributables.
A/B completed 60 runs: baseline 30/30, modernization 29/30. The sole discordant case had an ambiguous output contract; one separately frozen clarification pair passed both versions. Original gate remains false; no broad equivalence or speedup is claimed. See full results, including workspace deviations, capped replies and timing/cache limitations.
Tem remains a personal-host agent, not a certified multi-tenant sandbox. Automatic durable pursuit, complete experimental growth/cloud/telemetry implementations, every external messaging/account integration and native Windows TUI behavior are outside these validation guarantees. Model-proposed criteria do not prove coverage of the entire goal; model verdicts do not prove execution. Local usage accounting is not provider account-wide quota or atomic per-goal USD reservation. See the feature ledger, upgrade guide and closeout validation for specific boundaries.
Release workflow produces six primary binaries (Linux x86/ARM server and desktop, macOS Intel/Apple Silicon), four legacy updater aliases and a checksum manifest. All asset hashes and alias identities were verified after downloading the published files.
README and artwork
The README retains a full feature tour with clearer explanations, setup, commands and architecture. All 18 illustrations now share Tem’s creator-approved hair, slim character construction and expression vocabulary in a cozy punk-science Den. Exact prompts, hashes and design guidelines are preserved in the repository. Drawn interfaces are conceptual artwork, not screenshots.
Merge record
PR #74 was merged with a maintainer-directed admin squash after all eight checks passed, at commit 10f4cc6. The creator confirmed primary-maintainer/direct-main authority in response to the review-gate question. This is not represented as an independent approving review or as proof that the repository has only one administrator.
Publication verification
Tag pipeline completed successfully. All 11 expected assets are present; every binary matches the published SHA-256 manifest and all four aliases match their primary binaries. The previous-version update smoke passed on macOS/aarch64, reporting temm1e 6.0.0 — commit: 10f4cc6. This is a native update-path check on that platform, not execution of every cross-platform binary.
Known dependency advisories
Compatible patches and removal of the redundant legacy S3 TLS/HTTP connector reduced cargo-audit vulnerability entries from 26 to 7; 12 additional warnings remain. Counts describe lockfile/advisory matches, not proven remote exploits. Residual versions already existed in 5.8.1: Discord’s older certificate-validation dependency, Linux xcb’s build-time XML parser and an RSA dependency without an available fix. The inspected Discord path does not configure CRLs; URI/wildcard constraint advisories still require tracking. See the complete review. A green advisory audit job is not a clean security audit. The creator delegated the residual-risk decision; the release owner chose publication with these inherited issues disclosed and transport migration left as follow-up.
Launch kit
The supplementary release assets include temm1e-v6-launch.png, the exact image-generation prompt and manifest, and DISCORD-POST.md for a ready-to-copy English announcement. These are additional to the 11 verified distribution assets.
The displayed launch artwork uses a smaller WebP copy; the original PNG remains available among the release assets.