You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Register Amp's smart mode as pstack's Amp family #279
On pro14 after Eric's 2026-11-06 Amp login (Amp CLI 0.0.1792123242-g03edc7), pstack's registered Amp family amp-deepseek-v4.1-flash and every official Amp mode tried (gemini-3.8-flash, glm-5.3-flash, gpt-6-astra-low) fail with a server agentMode validation error; only the built-in smart and rush modes answer. Amp lanes on the registered family therefore fail, read-only included. Eric chose on 2026-11-06 to register smart (and rush).
Acceptance:
registry/models.ts registers Amp's smart (and rush if it answers) as the Amp family, measured on this account, with the CLI version in the catalog note; the old family stays a kept predecessor or is removed per the released-pair rules.
A read-only smart lane can read files (its tools are apply_patch and shell_command, both rejected by today's read-only settings). If it cannot, the read-only settings allow the read path smart uses, without enabling writes; measured.
Live gate: one writers:amp case and one Amp read-only lane, nothing else.
Source: PR #276 (#269), which measured the writer on smart.
Activity