feat(cloud-agent): create GitHub-signed commits in cloud runs

[tatoalo]

Problem

The cloud agent must create GitHub-signed commits across both the Claude and Codex adapters

Changes

Wires the git_signed_commit MCP tool into the agent:

• a shared tool definition (signed-commit-shared.ts) used by both adapters
• claude adapter support
• codex adapte support
• cloud system prompt updated to stage with git add and commit through the tool

[tatoalo]

• feat(cloud-agent): create GitHub-signed commits in cloud runs #2283 👈 (View in Graphite)
• feat(cloud-agent): add createSignedCommit for GitHub-signed commits #2282
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[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/codex/codex-agent.ts:587-590
The `meta?.taskId ?? meta?.persistence?.taskId` resolution pattern is duplicated verbatim in both `claude-agent.ts` (line 1101) and here. Extracting it to a small helper in `signed-commit-shared.ts` (or `utils/common.ts`) would satisfy the OnceAndOnlyOnce rule and keep the two adapters in sync if the fallback chain ever changes.

```suggestion
  private applySignedCommit<
    T extends { cwd?: string; mcpServers?: McpServer[]; _meta?: unknown },
  >(request: T, meta: NewSessionMeta | undefined): T {
    const taskId = resolveTaskId(meta);
```

_{Reviews (1): Last reviewed commit: "feat(cloud-agent): create GitHub-signed ..." | Re-trigger Greptile}

[joshsny]

can we do a standard MCP server for all these local tools we'll want, instead of one for each? small thing but it'd be nice to let other folks add tools easily to a general local mcp server

[tatoalo]

Merge activity

• May 21, 3:36 PM UTC: @tatoalo merged this pull request with Graphite.