T3 Code Status 0.3.0

Note

🤖 Codex responding on behalf of beastyrabbit

T3 Code Status 0.3.0 brings live question alerts to your OpenDeck keys. Pending input, approvals, and plan reviews appear as T3 sends them, without periodic cache reads.

Choose what each key shows

• Threads + questions keeps the working/open count visible and adds a blinking question mark when a thread needs you.
• Threads only shows the count without question alerts.
• Questions only keeps a faded question mark while clear, then flashes amber when input is needed.

Use a combined key or separate thread and question keys. Pair multiple T3 environments once and share their live connections across all keys.

Upgrade from 0.2.x

This release replaces automatic local-cache access with explicit read-only pairing. Install the new plugin package, open T3 Settings → Connections, enable Network access if pairing controls are hidden, and create a Read only link. Paste the complete link into the OpenDeck key settings within five minutes. Existing keys remain usable; the old refresh interval no longer applies.

Settings at a narrower width. Screenshots and animation use synthetic data from the reviewed release build.

Connection failures retry automatically. Each reconnect loads a fresh snapshot before showing live totals. If an environment is unavailable, the key shows its connection state instead of an incomplete count.

T3's current authorization lasts about 30 days. An uninterrupted stream may stay connected longer, but reconnecting after expiry requires a fresh pairing link. Automatic authorization renewal is not available in this flow.

Permissions and compatibility

Credentials are stored separately from OpenDeck profiles, with owner-only permissions on Unix and the user profile's ACLs on Windows. T3's read-only permission also permits reading files and conversations; this plugin requests only the shell status stream.

The plugin uses T3's existing first-party interface, not a versioned public SDK. It uses a three-day settlement default and does not import custom sidebar settlement preferences or pull-request state, so counts can differ from the T3 sidebar.

The new connection flow passed local HTTP/WebSocket integration tests and browser checks with synthetic data. It has not yet been exercised against a real T3 server or physical deck. The repository also adds broad OpenGrep analysis for pull requests.

Downloads

• com.beastyrabbit.t3-code-status.streamDeckPlugin: normal package for Linux, macOS, and Windows.
• com.beastyrabbit.t3-code-status-opendeck-setup.tar.gz: optional Linux setup helper.
• SHA256SUMS: checksums for both packages.

Node.js 20 or newer is required on the OpenDeck host. See the README for installation and provenance verification.

Built from da5a3c00e2012a7dcc1cc00a8abe2e0e7aa9196f. Build and portable checks passed; downloaded assets passed checksum and provenance verification. The workflow's final draft-metadata check failed after creating the draft, then passed when repeated against GitHub's API before publication.

Implemented in #1. Full changelog.

T3 Code Status 0.2.1

T3 Code Status 0.2.1

This patch fixes the red ERR state caused by current T3 Code cache files and lets the OpenDeck key recover automatically after T3 Code exits or its cache is temporarily unavailable.

Fixed

• Read both V8 serialization formats observed in T3 Code caches, versions 15 and 16.
• Retry every five seconds while T3 Code is offline or the cache cannot be read.
• Return to each key's configured refresh interval after recovery.
• Keep multiple visible status keys on a consistent recovery cycle.

Upgrade

Install com.beastyrabbit.t3-code-status.streamDeckPlugin through OpenDeck's plugin manager. Existing keys and refresh settings need no migration.

The plugin does not launch T3 Code. It reconnects automatically after T3 Code is running and its local cache is readable again.

Files

• com.beastyrabbit.t3-code-status.streamDeckPlugin is the normal OpenDeck package.
• com.beastyrabbit.t3-code-status-opendeck-setup.tar.gz is the optional Linux setup helper.
• SHA256SUMS contains checksums for both packages.

Built and checked from source commit 0e3388e732dd36871991916783c4ef4209506d8a. GitHub Actions published provenance attestations for all three files.

Full changelog: v0.2.0...v0.2.1

T3 Code Status 0.2.0

T3 Code Status 0.2.0

See the state of open T3 Code work on one OpenDeck key. The key shows the number of open top-level threads that are currently working, such as 4/7, and uses a red-to-yellow-to-green gradient for the ratio.

Included

• Reads T3 Code's local shell cache across connected environments.
• Counts Starting and Working as active work and keeps waiting threads in the total.
• Uses a 60-second refresh interval by default. Set 5 to 300 seconds in the Property Inspector, or press the key for an immediate refresh.
• Installs as a normal OpenDeck plugin on Linux, macOS, and Windows when system Node.js 20 or newer is available.
• Includes an optional Linux setup archive that installs the plugin and places the key in the first free slot of the Default profile.
• Needs no T3 account, pairing code, access token, external server, or network connection to T3.

Compatibility and limits

Linux is tested end to end with OpenDeck 2.14.0, T3 Code Alpha 0.0.36, and a physical Stream Deck. The T3 reader also connected to live T3 Code Alpha data on Windows 11 and macOS 26 on Apple silicon, and both platforms run the CI checks. OpenDeck itself has not yet been tested on those two probe machines. Linux Flatpak is not yet tested; it needs a system Node.js outside the Flatpak sandbox.

T3 Code does not include pull-request settlement state in the local shell snapshot. A thread whose settlement depends only on a pull request can therefore remain in the total until T3 Code writes a corresponding local state.

Files

• com.beastyrabbit.t3-code-status.streamDeckPlugin is the file to install through OpenDeck.
• com.beastyrabbit.t3-code-status-opendeck-setup.tar.gz is the optional Linux setup helper.
• SHA256SUMS contains checksums for both files.

The packages were built and checked from source commit 2281bc2e18b1bdea50254af95cfa23561a5a63ed. GitHub Actions published build provenance attestations for all three assets.