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/skills/verify-open-pstack/features/recipes.ts
Original file line number Diff line number Diff line change
Expand Up @@ -483,7 +483,7 @@ const setup: Case[] = [{
const sheet = join(f.configHome, 'pstack-models.md'), assertions = [loaded(record, 'pstack:setup-pstack'), await written(record, sheet)];
const text = await readFile(sheet, 'utf8'), descriptors = text.match(DESCRIPTOR) ?? [];
if (!descriptors.length || descriptors.some(d => d !== SETUP_DESCRIPTOR)) throw new Error('sheet-descriptors-mismatch');
if (!Bun.deepEquals(settingLines(text), [FULL_ACCESS_SETTING])) throw new Error('setting-not-full-access');
if (!Bun.deepEquals(settingLines(text).filter(line => line.startsWith(SETTING)), [FULL_ACCESS_SETTING])) throw new Error('setting-not-full-access');
return { assertions: [...assertions, `sheet:${SETUP_DESCRIPTOR}`, `setting:${FULL_ACCESS_SETTING}`], files: [sheet] };
},
}, {
Expand Down
8 changes: 8 additions & 0 deletions .claude/skills/verify-open-pstack/scripts/catalog.test.ts
Original file line number Diff line number Diff line change
Expand Up @@ -310,6 +310,14 @@ test('the configure case answers yes to full access and requires that setting wi
}
});

test('the configure case keeps another provider\'s writer setting line that setup preserves', async () => {
const f = await fixture('claude'), c = setupCase('configure'), installed = await readCatalog(location);
const written = `# pstack model configuration\n\n${[...installed.defaults].map(([role, lanes]) =>
`${role}: ${lanes.map(lane => lane.includes(':') ? 'claude:opus@high' : lane).join(', ')}`).join('\n')}\nmuse writer sandbox: full-access\n${FULL_ACCESS}`;
await writeFile(join(f.dir, 'pstack-models.md'), written);
expect((await c.assert(record('claude', 'pstack:setup-pstack'), f)).assertions).toContain('setting:codex writer sandbox: full-access');
});

test('the configure case starts from the daily sheet with only its setting line removed, so setup asks', async () => {
const f = await fixture('claude'), c = setupCase('configure'), path = join(f.dir, 'pstack-models.md');
await c.prepare!(f);
Expand Down
2 changes: 1 addition & 1 deletion .claude/skills/verify-open-pstack/scripts/core.test.ts
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,7 @@ describe('registry and ownership', () => {
});
test('the shared recipe implementation reaches every implemented recipe and preserves project proof', () => {
const path = '.claude/skills/verify-open-pstack/features/recipes.ts';
const expected = [...both('catalog', 'setup', 'runner', 'shipped-tools', 'hook:startup', 'project-skill',
const expected = [...both('catalog', 'setup', 'runner', 'shipped-tools', 'hook:startup', 'project-skill', 'writers',
...registry.skills.map(skill => `skill-invocation:${skill}`)), 'claude:agent-preload:poteto-agent'].sort();
for (const file of [{ filename: path }, { filename: 'docs/moved.md', previous_filename: path }]) {
const s = classify([file], registry);
Expand Down
2 changes: 1 addition & 1 deletion .claude/skills/verify-open-pstack/scripts/core.ts
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ export function classify(files: ChangedFile[], registry: Registry): Selection {
features.add('codex:assets:codex'); covered = true;
}
const sharedRecipe = path === '.claude/skills/verify-open-pstack/features/recipes.ts';
if (sharedRecipe) both('catalog');
if (sharedRecipe) both('catalog', 'writers');
const catalog = registry.catalog.some(p => matches(path, p));
if (catalog) { both('catalog', 'setup', 'runner'); covered = true; }
if (sharedRecipe || (!catalog && registry.shared.some(p => matches(path, p)))) {
Expand Down
6 changes: 3 additions & 3 deletions plugins/pstack/skills/poteto-mode/references/model-catalog.md
Original file line number Diff line number Diff line change
Expand Up @@ -188,9 +188,9 @@ The runner refuses an access mode outside a provider's Access modes cell before
- No agy writer is confined, so a writer needs the model sheet's opt-in (`isolated-write-full-access`); the runner refuses a bounded `isolated-write` lane before launch. On Antigravity CLI 1.5.2, `--mode auto` is not available for the measured account and falls back to the default mode, `--mode accept-edits` denies shell, and `--sandbox` blocks shell writes even in the cwd. An opted-in writer passes `--dangerously-skip-permissions`. Measured on macOS in a linked worktree under the home directory, whose main repository and a sibling directory sat beside it: edits, shell writes and a Python run inside the worktree succeeded, and the edit tool and the shell wrote into every outside target, including the main repository's shared `.git`, a home directory, `/tmp` and `$TMPDIR`.
- Antigravity CLI 1.5.2 loads the run-owned agent but ignores its `tools` list: the `init` event of a read-only lane listed 60 tools, among them web search, the browser and subagents. The approval policy still denied writes in a read-only lane.
- Headless agy cannot ask for approval. The first tool that needs it is denied, and the turn ends with exit 0, `status: "SUCCESS"` and a `denied_actions` list. Any `response` text is a preamble written before the denied tool, so the runner records a non-empty `denied_actions` as `child-failed`/70 whatever the response says.
- Each lane writes a run-owned agent file, `.agents/agents/pstack-lane.md`, in its private `<receipt>.provider/` directory (0700, the file 0600), and runs `--add-dir <that directory> --agent pstack-read-only`. The agent declares only `view_file`, no MCP servers and no skills. The lane keeps `view_file` and `manage_task` and loses web search, `read_url_content`, subagents, `schedule`, `send_message` and the browser. If the file is missing, agy exits 1 with `unknown agent`.
- An agy lane runs in any directory, and the configuration it finds there applies as it is. agy runs the hooks and MCP servers in `.agents/`, `.agent/`, `_agents/` and `_agent/` directories in the cwd and each parent up to the git root, or up to `/` outside a repository, with no trust check, and loads their rules and skills. So a lane whose cwd is under the home directory and outside any git repository, or in a repository rooted at the home directory, also loads the home directory's own `~/.agents/` and its siblings. No flag stops them. A repository agent named `pstack-read-only` replaces the run-owned one.
- No flag turns off the operator's own configuration. `~/.gemini/GEMINI.md` loads as a global rule, and host skills and agy plugin hooks under `~/.gemini/` still load in every lane. The run-owned agent limits only the lane's tools.
- Each lane writes a run-owned agent file, `.agents/agents/pstack-lane.md`, in its private `<receipt>.provider/` directory (0700, the file 0600), and runs `--add-dir <that directory> --agent pstack-lane`. The agent declares no MCP servers and no skills, and its `tools` list names only `view_file` for a read-only lane and adds the write and shell tools for a writer. Antigravity CLI 1.3.6 honoured that list, and a read-only lane kept only `view_file` and `manage_task`. If the file is missing, agy exits 1 with `unknown agent`.
- An agy lane runs in any directory, and the configuration it finds there applies as it is. agy runs the hooks and MCP servers in `.agents/`, `.agent/`, `_agents/` and `_agent/` directories in the cwd and each parent up to the git root, or up to `/` outside a repository, with no trust check, and loads their rules and skills. So a lane whose cwd is under the home directory and outside any git repository, or in a repository rooted at the home directory, also loads the home directory's own `~/.agents/` and its siblings. No flag stops them. A repository agent named `pstack-lane` replaces the run-owned one.
- No flag turns off the operator's own configuration. `~/.gemini/GEMINI.md` loads as a global rule, and host skills and agy plugin hooks under `~/.gemini/` still load in every lane.
- The lane passes the base allowlist and nothing else. The login is in the macOS keychain, found through `HOME`, so a run-owned `HOME` would be logged out. `GEMINI_API_KEY` did not authenticate and is not passed.
- The preflight runs `agy models` and passes when it exits 0 and a line's first tab-separated field is the lane's CLI model ID. Exit 0 without that line is `unavailable-model`/69. Exit 1 with `Please sign in` is `unauthenticated`/77. Any other output is `child-failed`/70.
- The prompt goes to stdin as one stream-json line, `{"event":"user","message":{"role":"user","content":<prompt>}}`, with `--input-format stream-json --output-format stream-json`. The reply is the `result` event's `response` without its trailing newline. The session is `conversation_id`, and usage is `usage`, with `thinking_tokens` as reasoning and `cache_read_tokens` as cached input. agy reports no cost.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -138,9 +138,9 @@ export const agy = adapter({
"No agy writer is confined, so a writer needs the model sheet's opt-in (`isolated-write-full-access`); the runner refuses a bounded `isolated-write` lane before launch. On Antigravity CLI 1.5.2, `--mode auto` is not available for the measured account and falls back to the default mode, `--mode accept-edits` denies shell, and `--sandbox` blocks shell writes even in the cwd. An opted-in writer passes `--dangerously-skip-permissions`. Measured on macOS in a linked worktree under the home directory, whose main repository and a sibling directory sat beside it: edits, shell writes and a Python run inside the worktree succeeded, and the edit tool and the shell wrote into every outside target, including the main repository's shared `.git`, a home directory, `/tmp` and `$TMPDIR`.",
"Antigravity CLI 1.5.2 loads the run-owned agent but ignores its `tools` list: the `init` event of a read-only lane listed 60 tools, among them web search, the browser and subagents. The approval policy still denied writes in a read-only lane.",
"Headless agy cannot ask for approval. The first tool that needs it is denied, and the turn ends with exit 0, `status: \"SUCCESS\"` and a `denied_actions` list. Any `response` text is a preamble written before the denied tool, so the runner records a non-empty `denied_actions` as `child-failed`/70 whatever the response says.",
"Each lane writes a run-owned agent file, `.agents/agents/pstack-lane.md`, in its private `<receipt>.provider/` directory (0700, the file 0600), and runs `--add-dir <that directory> --agent pstack-read-only`. The agent declares only `view_file`, no MCP servers and no skills. The lane keeps `view_file` and `manage_task` and loses web search, `read_url_content`, subagents, `schedule`, `send_message` and the browser. If the file is missing, agy exits 1 with `unknown agent`.",
"An agy lane runs in any directory, and the configuration it finds there applies as it is. agy runs the hooks and MCP servers in `.agents/`, `.agent/`, `_agents/` and `_agent/` directories in the cwd and each parent up to the git root, or up to `/` outside a repository, with no trust check, and loads their rules and skills. So a lane whose cwd is under the home directory and outside any git repository, or in a repository rooted at the home directory, also loads the home directory's own `~/.agents/` and its siblings. No flag stops them. A repository agent named `pstack-read-only` replaces the run-owned one.",
"No flag turns off the operator's own configuration. `~/.gemini/GEMINI.md` loads as a global rule, and host skills and agy plugin hooks under `~/.gemini/` still load in every lane. The run-owned agent limits only the lane's tools.",
"Each lane writes a run-owned agent file, `.agents/agents/pstack-lane.md`, in its private `<receipt>.provider/` directory (0700, the file 0600), and runs `--add-dir <that directory> --agent pstack-lane`. The agent declares no MCP servers and no skills, and its `tools` list names only `view_file` for a read-only lane and adds the write and shell tools for a writer. Antigravity CLI 1.3.6 honoured that list, and a read-only lane kept only `view_file` and `manage_task`. If the file is missing, agy exits 1 with `unknown agent`.",
"An agy lane runs in any directory, and the configuration it finds there applies as it is. agy runs the hooks and MCP servers in `.agents/`, `.agent/`, `_agents/` and `_agent/` directories in the cwd and each parent up to the git root, or up to `/` outside a repository, with no trust check, and loads their rules and skills. So a lane whose cwd is under the home directory and outside any git repository, or in a repository rooted at the home directory, also loads the home directory's own `~/.agents/` and its siblings. No flag stops them. A repository agent named `pstack-lane` replaces the run-owned one.",
"No flag turns off the operator's own configuration. `~/.gemini/GEMINI.md` loads as a global rule, and host skills and agy plugin hooks under `~/.gemini/` still load in every lane.",
"The lane passes the base allowlist and nothing else. The login is in the macOS keychain, found through `HOME`, so a run-owned `HOME` would be logged out. `GEMINI_API_KEY` did not authenticate and is not passed.",
"The preflight runs `agy models` and passes when it exits 0 and a line's first tab-separated field is the lane's CLI model ID. Exit 0 without that line is `unavailable-model`/69. Exit 1 with `Please sign in` is `unauthenticated`/77. Any other output is `child-failed`/70.",
"The prompt goes to stdin as one stream-json line, `{\"event\":\"user\",\"message\":{\"role\":\"user\",\"content\":<prompt>}}`, with `--input-format stream-json --output-format stream-json`. The reply is the `result` event's `response` without its trailing newline. The session is `conversation_id`, and usage is `usage`, with `thinking_tokens` as reasoning and `cache_read_tokens` as cached input. agy reports no cost.",
Expand Down
Loading