Tibo Rush 0.2.1

Tibo Rush 0.2.1

A documentation and metadata release. No source, preset, script or test changed since 0.2.0, so behavior and state are identical.

What changed

• The English README is now a full reference, and the Chinese reference lives in README.zh-CN.md. Each page links to the other.
• Both READMEs include short Oh My Pi and Pi recordings. They were made in an isolated environment with no credentials, so they show how a failed switch is reported rather than a successful one.
• The package and marketplace description is now "One-switch model and service-tier modes for Oh My Pi and Pi".
• Install commands and package names point at v0.2.1.

Upgrading from 0.2.0

The state directory, commands and policy format are unchanged. Reinstall or update the package, then /restart (OMP) or /reload (Pi) each open session.

Packages

• tibo-rush-omp-0.2.1.tgz: Oh My Pi adapter and shared core.
• tibo-rush-pi-0.2.1.tgz: Pi adapter and shared core.

Install one per host. See the README for steps.

Verified

• Offline tests and packaging checks.
• Real-host smoke tests against OMP 18.12.6 and Pi 1.4.0 on macOS, with no model calls.
• Both packages load in fresh isolated sessions.

Tibo Rush 0.2.0

Tibo Rush 0.2.0

The project is now Tibo Rush: one-switch subscription quota sprint modes for OMP and Pi.

Unified names

• Repository/product/package: tibo-rush / Tibo Rush.
• Peer host adapters and release archives: tibo-rush-omp, tibo-rush-pi.
• Both hosts expose /tibo-rush regular|fast|extreme|off|status.
• The standalone CLI is exclusively tibo-rush; the previous command aliases are removed.
• Shared state defaults to ~/.tibo-rush; override with TIBO_RUSH_HOME.
• Presets, source symbols, prompt/status/journal namespaces, fixtures, docs, package manifests and build paths use the new name.

Breaking upgrade from 0.1.0 or the hand-installed extension

Before uninstalling, replacing or loading adapters, run the old version's OFF command and confirm every connected and offline/resumed session has restored its baseline. Then uninstall/remove old extension entries and CLI links, install the new packages, and restart/reload each host. Do not load both versions together.

Old state and recovery data are not moved, deleted, imported or rewritten. Do not copy old state directories or rewrite journal markers to simulate migration. Reconfigure model policies manually if needed. Existing 0.1.0 tags and release artifacts remain historical records.

Install

OMP:

/marketplace add happyfeetw/tibo-rush
/marketplace install tibo-rush-omp@tibo-rush
/restart

Pi:

pi install git:github.com/happyfeetw/tibo-rush@v0.2.0

Then /reload in existing Pi sessions. Each attached host-specific tarball can also be extracted and installed from a local directory.

Scope

This is a naming cutover; the switching and restoration algorithms remain unchanged. OMP 18.12.5/18.12.6 and Pi 1.4.0 are the supported/tested host APIs. Pi does not claim OMP role/subagent routing. Priority is a bounded native Codex request, not guaranteed server acceptance, throughput or quota savings.

No live user installation or recovery state was automatically migrated. This GitHub release is not npm publication or Pi gallery listing.

Verification

• 19 isolated behavior tests passed.
• Real OMP 18.12.5 and 18.12.6 each passed all 22 smoke scenarios, including restoration metadata and native timeout gates under the new names.
• Real Pi 1.4.0 passed all eight command/model/thinking/payload/recovery checks.
• Actual OMP TUI /tibo-rush extreme and /tibo-rush off applied and restored the original state; no old brand appeared on that surface.
• Both host-specific archives built with the expected file whitelist and executable CLI.
• No network model calls were used. Provider-side priority acceptance, throughput and billing were not re-probed.

Tibo Impact 0.1.0

Tibo Impact 0.1.0

Tibo Impact is the product; tibo-impact-omp and tibo-impact-pi are peer host adapters. Both expose the same /tibo-impact regular|fast|extreme|off|status commands.

• Shared, configurable presets and cross-session state; TIBO_IMPACT_HOME defaults to ~/.tibo-impact.
• OMP: main model/thinking/service tier, role and agent routing, exact baseline restoration with host flush confirmation, branch/cancel handling, truthful drift/error state.
• Pi: main model/thinking and a bounded native Codex priority payload hook. No OMP role or subagent routing is claimed.
• tibo-impact CLI plus the existing omp-impact command alias.
• MIT licensed. No credentials, transcripts, client state or restoration baselines included.

Install

OMP:

/marketplace add happyfeetw/tibo-impact
/marketplace install tibo-impact-omp@tibo-impact
/restart

Pi:

pi install git:github.com/happyfeetw/tibo-impact@v0.1.0

Then /reload in existing Pi sessions. The attached host-specific tarballs can also be extracted and installed from a local directory; do not install duplicate copies.

Verification and limits

• 19 isolated library/CLI behavior tests.
• OMP 18.12.5 and 18.12.6: 22 real-RPC checks each, including mode changes, cancellation/branch/fork, auto/unset thinking, drift, failed host writes, crash recovery, inherited handoff publication failures and actual native 30-second BEFORE-hook timeout cancellation.
• Pi 1.4.0 real RPC: mode/thinking changes, busy preservation, stale payload vs new OFF/active revision, malformed policy OFF and cold recovery.
• OMP+Pi simultaneous shared-state switching and independent original-state restoration.
• Actual OMP TUI extreme/OFF interaction.
• No network model requests in these checks. Priority server acceptance, latency and billing were not paid-probed.

Runtime host validation was performed on macOS; other OS combinations and SDK-injected remote session stores are not certified. OMP adapter compatibility is deliberately guarded to the two tested versions. Bundled model IDs are examples: configure policies for models actually available in each host.

Active OMP /new waits for an idle-safe original-state restoration; a busy owned session explicitly cancels that new-session request. Unrecoverable dual-store handoff failure is reported as blocked recovery, never successful OFF. Durability follows host flush semantics, not power-loss/fsync guarantees.

This is not an official OpenAI, Tibo, OMP or Pi project. It neither predicts nor redeems quota resets. GitHub release availability is not npm publication or Pi gallery listing.

Users of the earlier hand-installed OMP extension must first complete OFF restoration through the old version, remove its entry, and then install the package. The old state directory is not automatically migrated or deleted.