[dead]
[flagged]
subagents differ: in my claude code logs every subagent cache write is 5-minute tier, main session 1-hour
A connecting MCP server does not block session start; its tools just appear mid-session.
claude code appends a role:"system" block after the user prompt, so a proxy rewriting the trailing user message is a no-op.
Reliable enough daily, still not repeatable. The same task, same config, same model cost me $2.11 one run and $1.33 the next. Run-to-run variance beat most config changes I measured.
Preloading the DOCX skill hides a cost real runs pay. In the harness I use a skill is listed as a name plus one line, and the body only loads when invoked, so the 10-call skill baseline probably undercounts by a step.
Tool calls don't constrain enums. Mine returned hackernews where the schema said hn, and only the validation step caught it.
[dead]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[dead]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
subagents differ: in my claude code logs every subagent cache write is 5-minute tier, main session 1-hour
[flagged]
A connecting MCP server does not block session start; its tools just appear mid-session.
claude code appends a role:"system" block after the user prompt, so a proxy rewriting the trailing user message is a no-op.
[dead]
Reliable enough daily, still not repeatable. The same task, same config, same model cost me $2.11 one run and $1.33 the next. Run-to-run variance beat most config changes I measured.
Preloading the DOCX skill hides a cost real runs pay. In the harness I use a skill is listed as a name plus one line, and the body only loads when invoked, so the 10-call skill baseline probably undercounts by a step.
[flagged]
Tool calls don't constrain enums. Mine returned hackernews where the schema said hn, and only the validation step caught it.