Practice — Headless Mode, CI Automation & the Agent SDK (11 questions)
Why a CI Job Needs --bare, Not Just -p Permalink →
Your team runs claude -p "summarize the failing tests" --output-format json
inside a GitHub Actions job that checks out a fork's PR branch (an
external contributor's fork, not your own repository) to generate a
test-failure summary as a comment.
- Without
--bare, what specifically can happen in this job that wouldn't happen in an ordinary interactiveclaudesession opened in a directory you've never trusted before? - Why doesn't Claude Code show the equivalent of a trust-dialog prompt
in this
-pinvocation the way it would interactively? - Rewrite the invocation to close this gap while still letting Claude read the test output and produce a summary.
Share this question
Why the Nightly Triage Job Opens Draft PRs, Not Merged Ones
Unlock this question →Session Strategy for a Multi-User SDK Service on Ephemeral Containers
Unlock this question →The Default Permission Mode When You Add -p Permalink →
A script runs claude -p "fix the failing test" with no
--permission-mode or --allowedTools flags set.
What permission mode does this headless run actually start in?
Share this question
Piping a Large Log File Into Headless Claude Code Permalink →
You want to analyze a 40MB build log with
cat build.log | claude -p "explain the failure".
What actually happens?
Share this question
Why an SDK App With 300 MCP Tools Doesn't Load Them All Upfront Permalink →
An Agent SDK application connects to an enterprise MCP gateway exposing roughly 300 tools.
By default, how does the SDK handle loading those tool definitions into context?
Share this question