Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
"name": "t3-pstack",
"source": "./plugins/pstack",
"description": "pstack for T3 Code: rigorous agent workflows whose panels and fan-outs run across model families through T3. Original pstack by Lauren Tan (poteto).",
"version": "2.2.4"
"version": "2.2.5"
}
]
}
16 changes: 16 additions & 0 deletions CHANGES.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,22 @@

This file is the release changelog, with one `## <version> - <title>` entry per release, newest first. The Cursor-to-T3 rewrite rules live in [`tools/substitutions.json`](tools/substitutions.json), and the [sync boundary](CONTRIBUTING.md#the-sync-boundary) in `CONTRIBUTING.md` defines how a change to upstream's skill content is declared.

## 2.2.5 - The installer pins each Codex home to the release tag, so Codex's own updates no longer turn the hook off

On Codex 0.164 and later, a plugin hook's trust covers every file in the installed plugin, as 2.2.3 described. Each time a Codex app-server starts, such as the one T3 runs, Codex's marketplace auto-upgrade moved each home's `t3-pstack` marketplace to the latest commit on `main` and reinstalled the plugin from it. So each release, and each other commit that changed the plugin's files, turned the session-start hook off with `plugin contents changed; hook approval required` until someone reran the installer. 2.2.3 left this as it was.

`install` and `update` now pin each Codex home's `t3-pstack` marketplace to this release's tag. In that home's `config.toml`, the `[marketplaces.t3-pstack]` table gets one more line, `ref = "v2.2.5"`, and its `source` stays as it was. Codex's auto-upgrade fetches again only when the hash that `git ls-remote` reports for the configured ref differs from the commit it installed. For a lightweight tag, which every t3-pstack release tag is, the two stay equal, so it leaves the home where it is. A release reaches a Codex home only when `update` runs, and that run trusts the hook again. A home pinned to an earlier tag moves to this one. `codex plugin marketplace add --ref` refuses a marketplace that is already added, so the installer writes the ref through the Codex app-server's config writer, as it writes the hook's trust, and then runs `codex plugin marketplace upgrade t3-pstack`, which fetches the tag and reinstalls the plugin from it. When Codex cannot fetch the tag, as from a fork that never pushed it, or from `main` before the release is tagged, the installer writes the old ref back, updates the home as before, and says so. `doctor` then fails the home's pin, and each run exits 1, until the source has the tag. A marketplace from a local directory has no tag and stays unpinned. Claude Code homes do not change.

`doctor` has a new Codex check, `marketplace pin`. It fails a home that is unpinned or pinned to another tag, as in `marketplace pin: none, expected v2.2.5`, and its fix reruns the installer with the run's `--source`. On a local directory it passes with `none, since a local directory has no tag`.

To follow `main` again, delete the `ref` line from `[marketplaces.t3-pstack]` in that home's `config.toml`. Codex then moves the home to the latest commit on `main` at its next start. The next `install` or `update` pins it again, and `doctor` fails it until then. A ref set by hand, such as `main`, is replaced the same way.

In throwaway homes on macOS with Codex 0.167.0, a repository in the test folder served as `https://github.com/chhoumann/t3-pstack.git` through the global Git config. With 2.2.3's installer, a home set up from the default source moved from 2.2.3 to a newer commit on `main` at 9.9.9, through `codex plugin marketplace upgrade` and through a bare app-server start within 0.8 seconds, and its hook read `modified` both times. With this release's installer, the same home read `ref = "v2.2.5"`. `codex plugin marketplace upgrade` printed `All configured Git marketplaces are already up to date.`, an app-server ran for 20 seconds without moving it, the hook stayed trusted, and `doctor` passed. A new end-to-end suite runs these checks from the default source, a GitHub `--source`, a Git URL `--source`, and a local directory, with homes that Codex's own CLI set up unpinned and pinned to an older tag, a source without the tag, and a second run that changes nothing. Against 2.2.3's `codex.mjs` all 5 of its tests fail. On macOS with Codex 0.167.0, Claude Code 2.1.319, and Bun 1.4.4, the installer's end-to-end test passes 18 of 18, and `GIT_CONFIG_GLOBAL=/dev/null bun test tests/` passes 554, skips 56, and fails 0.

Users who do nothing keep today's behaviour. Run `npx -y github:chhoumann/t3-pstack update` to pin each Codex home. Neither hooks file changes. This is a patch release.

Thanks to @rma1k0 for the report and its evidence ([#56](https://github.com/chhoumann/t3-pstack/issues/56)).

## 2.2.4 - poteto-mode runs interrogate only for a contested design, as Lauren's pstack does

poteto-mode no longer runs `interrogate` before every pull request. Since 1.0.1 it sent each bug fix, feature, or refactoring diff to the `interrogate reviewers` panel before Opening a PR, and 1.0.6 added a review loop to that gate: later rounds reviewed only the fix diff, a `feature, refactoring` delegate ran the real artifact after each fix round, and the loop stopped after three rounds. The gate was always the port's own addition and never Lauren's text. Through 1.0.14 it lived in the port's `t3-tools.md`, and from 2.0.0-rc.1 it was an anchored insert in `tools/substitutions.json` after Lauren's contested-design trigger. At `c742dd6` Lauren's poteto-mode runs `interrogate` only for a contested design, and the Feature playbook's step 7 says "If the design is contested, `interrogate` before shipping." So in a T3 session every bug fix, feature, and refactoring ran a multi-model adversarial panel that Lauren's pstack saves for a contested design ([#65](https://github.com/chhoumann/t3-pstack/issues/65)).
Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ Dependabot keeps the pinned action SHAs current. The vendored scripts' one runti

Plugin auto-update installs **by version number**, not by tracking `main`. A skill fix merged without a version bump is inert on every installed copy. The bump is three steps: edit the root `VERSION` file, add a `CHANGES.md` entry under a `## <version> - <title>` heading, and run `bun tools/generate.mjs` to stamp the manifests. Forgetting any of the three fails CI.

Versions follow semantic versioning, and each sync of Lauren's pstack is its own release. A patch release (2.0.1) carries fixes and reworded text, whether Lauren's or the port's. A minor release (2.1.0) adds a skill, a capability, or a harness. A major release (3.0.0) is for a change the user must act on, such as rerunning the installer or editing the model sheet. When a release spans more than one kind, the largest wins. The `CHANGES.md` entry of a sync names the pstack version it moves to. Each release gets a `v<version>` tag and a GitHub release whose notes are its `CHANGES.md` entry.
Versions follow semantic versioning, and each sync of Lauren's pstack is its own release. A patch release (2.0.1) carries fixes and reworded text, whether Lauren's or the port's. A minor release (2.1.0) adds a skill, a capability, or a harness. A major release (3.0.0) is for a change the user must act on, such as rerunning the installer or editing the model sheet. When a release spans more than one kind, the largest wins. The `CHANGES.md` entry of a sync names the pstack version it moves to. Each release gets a `v<version>` tag and a GitHub release whose notes are its `CHANGES.md` entry. Make the tag a lightweight one, as `git tag v<version>` makes without `-a`, `-s`, or `tag.gpgSign`, and push it as soon as the release merges. The installer pins each Codex home's marketplace to it, and until it exists, `update` leaves each Codex home on the ref it had. Codex compares the hash that `git ls-remote` reports for the tag with the commit it installed, and for an annotated tag they never match, so every Codex start would clone the marketplace and reinstall the plugin again.

## Commit and PR style

Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,11 @@ npx -y github:chhoumann/t3-pstack update
npx -y github:chhoumann/t3-pstack doctor
```

`npx -y github:chhoumann/t3-pstack` runs the installer from the latest commit on `main`. That is the rolling channel, the same one each home's marketplace auto-updates from. To run one release's installer, name its tag, as in `npx -y github:chhoumann/t3-pstack#v2.2.4 doctor`.
`npx -y github:chhoumann/t3-pstack` runs the installer from the latest commit on `main`. Each Claude Code home's marketplace auto-updates from `main` too, and each Codex home's marketplace stays on the release tag the installer pinned. To run one release's installer, name its tag, as in `npx -y github:chhoumann/t3-pstack#v2.2.5 doctor`.

`install` and `update` are the same command, and a second run changes nothing. With Node 20 or later, it installs or updates the `t3-pstack@t3-pstack` plugin in every Claude Code and Codex config home T3 can run: `~/.claude` and `~/.codex`, `$CLAUDE_CONFIG_DIR` and `$CODEX_HOME`, and the home of each `claudeAgent` and `codex` instance in T3's settings, disabled ones included. Name any other home with `--claude-home <dir>` or `--codex-home <dir>`. Each home's `t3-pstack` marketplace must come from `chhoumann/t3-pstack`, or from `--source <owner/repo|git URL|dir>` on the same run, and a home whose marketplace has another source is left as it is. A run never switches a home's source, so a home already on `chhoumann/t3-pstack` stays on it under another `--source`, and `doctor` warns and prints the commands that move it. A local directory needs a path such as `./t3-pstack`, since `owner/repo` always means GitHub. On Codex it also trusts t3-pstack's session-start hook, once its hooks file is the one this release pins. Codex runs a plugin's hook only once it is trusted, and T3's Codex sessions never ask, so without this step the hook never runs. Codex 0.164 and later tie that trust to every file in the installed plugin, so each release turns the hook off, even one Codex's own auto-update installs, until `update` runs again. Run `update` after each release.
`install` and `update` are the same command, and a second run changes nothing. With Node 20 or later, it installs or updates the `t3-pstack@t3-pstack` plugin in every Claude Code and Codex config home T3 can run: `~/.claude` and `~/.codex`, `$CLAUDE_CONFIG_DIR` and `$CODEX_HOME`, and the home of each `claudeAgent` and `codex` instance in T3's settings, disabled ones included. Name any other home with `--claude-home <dir>` or `--codex-home <dir>`. Each home's `t3-pstack` marketplace must come from `chhoumann/t3-pstack`, or from `--source <owner/repo|git URL|dir>` on the same run, and a home whose marketplace has another source is left as it is. A run never switches a home's source, so a home already on `chhoumann/t3-pstack` stays on it under another `--source`, and `doctor` warns and prints the commands that move it. A local directory needs a path such as `./t3-pstack`, since `owner/repo` always means GitHub. On Codex it also trusts t3-pstack's session-start hook, once its hooks file is the one this release pins. Codex runs a plugin's hook only once it is trusted, and T3's Codex sessions never ask, so without this step the hook never runs. Codex 0.164 and later tie that trust to every file in the installed plugin, so each release turns the hook off until the installer trusts it again. So the installer pins each Codex home's `t3-pstack` marketplace to the release's tag, such as `v2.2.5`, and Codex's own auto-upgrade leaves that tag where it is. A release reaches a Codex home only when `update` runs, and that run trusts the hook again. A local directory has no tag, so a marketplace from one stays unpinned. Run `update` after each release.

`doctor` reports on the same homes and changes nothing itself: each marketplace's source, the installed version, whether its files are all there, whether it is enabled, the Codex hook's trust, Claude Code records that pin an old version, plain copies of the plugin's skills, and the model sheet. It exits 1 on any problem and prints a fix for each.
`doctor` reports on the same homes and changes nothing itself: each marketplace's source, each Codex marketplace's pin, the installed version, whether its files are all there, whether it is enabled, the Codex hook's trust, Claude Code records that pin an old version, plain copies of the plugin's skills, and the model sheet. It exits 1 on any problem and prints a fix for each.

Then run `/t3-pstack:setup-pstack` in a T3 thread on each machine. It writes the model sheet, `~/.config/t3-pstack/models.md`, with one T3 target per role (`<providerInstanceId>/<modelId>` plus that provider's options), and checks it against the machine's `orchestrator_capabilities`. Without a sheet, every role runs on the defaults in its skill's Models section.

Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
2.2.4
2.2.5
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "t3-pstack",
"private": true,
"version": "2.2.4",
"version": "2.2.5",
"description": "The installer and development tooling for t3-pstack, Lauren Tan's pstack rewritten in place for T3 Code. The plugin itself lives in plugins/pstack.",
"author": {
"name": "Christian Bager Bach Houmann",
Expand Down
2 changes: 1 addition & 1 deletion plugins/pstack/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "t3-pstack",
"displayName": "t3-pstack (pstack for T3 Code)",
"version": "2.2.4",
"version": "2.2.5",
"description": "pstack for T3 Code: Lauren Tan's pstack with its Cursor mechanics rewritten in place for T3, so subagents, panels, schedules, and PR watches dispatch through T3's orchestration and panels mix Claude, GPT, and Grok.",
"author": {
"name": "Christian Bager Bach Houmann",
Expand Down
2 changes: 1 addition & 1 deletion plugins/pstack/.codex-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "t3-pstack",
"version": "2.2.4",
"version": "2.2.5",
"description": "pstack for T3 Code on a Codex host: Lauren Tan's pstack with its Cursor mechanics rewritten in place for T3, so subagents, panels, schedules, and PR watches dispatch through T3's orchestration.",
"author": {
"name": "Christian Bager Bach Houmann",
Expand Down
Loading
Loading