Repository navigation
fix(server): agents find T3's pstack, and pstack is on by default - #117
Open
ScriptedAlchemy wants to merge 5 commits into
Open
ScriptedAlchemy wants to merge 5 commits into
ScriptedAlchemy wants to merge 5 commits into
Conversation
T3 turns off native pstack plugins in the sessions it starts, but its own pack only reached the agent through an explicit $pstack:<skill>. A plain "use pstack principles" left the agent with no copy, so it asked where pstack was and read a stale Cursor cache instead. A user message that names pstack without invoking a skill now gets a short locator naming T3's pack. Turn start and steering share one predicate, so a mention mid-turn is covered too. No workflow or role resolution runs. Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
T3 ships pstack built in, so new environments and settings that never chose now get it. An explicit off in Settings → Labs → Zack still wins. Co-Authored-By: Claude Opus 5.5 <[email protected]>
ScriptedAlchemy
changed the title
Codex stores a goal's text as its objective, so the pstack locator became part of the goal and could push it past Codex's length limit. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
T3 turns off native Codex and Claude pstack plugins in the sessions it starts, since its own pack replaces them. But that pack only reached the agent through an explicit
$pstack:<skill>. In a real thread, "use pstack principles" left a Codex agent with no copy. It asked the user where pstack was, then read a stale Cursor plugin cache. pstack was also off unless turned on in Labs.<t3_pstack>locator. The locator gives the pack path, says skills live at<pstack>/skills/<name>/SKILL.md, and says running a workflow with T3's model roles needs$pstack:<skill>. Nothing runs and no roles are resolved, since pstack skills are invocation-only by design. Turn start and steering now share onereferencesPstackpredicate. Before this, steering never expanded a plain mention. Agent-authored messages, notifications, and the pstack-off setting are unchanged.pstackEnablednow defaults totrue. Turning it off in Settings → Labs → Zack is saved and wins. Settings files never stored the old default, so an opt-out saved before this change reads as on again; that is intended, since pstack should be on for everyone, and turning it off again sticks./goalthat names pstack gets no locator, since Codex stores a goal's text as its objective.Tests: extended the PstackPack expansion case (it fails on
main) and the steeringplain-namerow. The ws config-stream toggle test now starts from the new default. Every test that references pstack or the settings defaults passes (server, contracts, shared, client-runtime, web, mobile), as doesvp run check:changed.🤖 Generated with Claude Code