feat(signed-commit): accept an optional cwd so the tool works on any clone

[joshsny]

Problem

The git_signed_commit MCP tool's ctx.cwd is bound once at session
creation: agent-server.ts passes this.config.repositoryPath ?? "/tmp/workspace"
into the new session and the local-tools MCP server captures that as
its LocalToolCtx.cwd. Every git invocation in createSignedCommit
runs against that bound cwd, so a task that clones a second repo (or
works in any checkout outside the original session cwd) can't commit
from it — git remote get-url origin runs from the wrong directory
and fails.

Changes

• Add an optional cwd field to signedCommitToolSchema.
• In the local-tool handler, resolve it via path.resolve(ctx.cwd, argCwd)
  (absolute paths pass through, relative paths join the session cwd),
  override the ctx, and strip cwd from the input forwarded to
  createSignedCommit so the lower-level API surface is unchanged.
• Default behavior is preserved: omit cwd and the tool still runs
  against the session cwd.

How did you test this?

• pnpm --filter @posthog/agent typecheck — clean.
• pnpm exec vitest run src/adapters/local-tools src/adapters/claude/mcp/local-tools
  passes. New signed-commit.test.ts covers: default-to-session-cwd,
  absolute override, relative resolution, that cwd isn't forwarded as
  a SignedCommitInput field, and the existing no-token error path.

Publish to changelog?

no

---

Created with PostHog Code

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
packages/agent/src/adapters/local-tools/tools/signed-commit.test.ts:41-76
**Prefer parameterised tests for cwd resolution cases**

The three cases testing how `args.cwd` resolves to the final `ctx.cwd` (absent, absolute, relative) share an identical shape — call handler, read `createSignedCommit.mock.calls[0][0].cwd`, assert equality. They could be collapsed into a single `it.each` table to avoid repeating the identical handler call and assertion three times while keeping each resolution case explicit and readable.

_{Reviews (1): Last reviewed commit: "style: apply biome formatter to signed-c..." | Re-trigger Greptile}

[greptile-apps]

_{Reviews (2): Last reviewed commit: "feat(signed-commit): accept an optional ..." | Re-trigger Greptile}