You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update CHANGELOG, README, and bump all package versions to 0.26.0.
Changes:
- Update CHANGELOG.md with custom tools support and Codex default model
- Add Custom Tools section to root README with comprehensive example
- Copy updated README to core package for npm distribution
- Bump version to 0.26.0 across all packages
- Update peer dependencies to @headless-coder-sdk/core@^0.26.0
This release includes custom tools infrastructure, Claude adapter
automatic MCP server conversion, and Codex adapter default model
update to gpt-5.2.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+64Lines changed: 64 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -235,6 +235,70 @@ In this workflow two reviewers (Claude, Codex) analyze the same commit in parall
235
235
236
236
---
237
237
238
+
## 🛠 Custom Tools (Claude)
239
+
240
+
The SDK provides a unified interface for creating custom tools that extend Claude's capabilities, following the Claude Agent SDK's MCP (Model Context Protocol) pattern:
const result =awaitthread.run("What's the weather in San Francisco? (37.7749, -122.4194)");
288
+
console.log(result.text);
289
+
```
290
+
291
+
**Key Features:**
292
+
-**Type-safe schemas** – Define input schemas with full TypeScript support
293
+
-**Tool name management** – Use `getToolName(server, tool)` for proper MCP naming (`mcp__{server}__{tool}`)
294
+
-**Selective permissions** – Control which tools Claude can use via `allowedTools`
295
+
-**Streaming support** – Custom tools work seamlessly with `runStreamed()`
296
+
-**Claude native** – Use Claude's native `tool()` and `createSdkMcpServer()` directly if preferred
297
+
298
+
See `examples/src/claude-custom-tools.test.ts` for comprehensive examples including calculator, formatter, and multi-tool workflows.
299
+
300
+
---
301
+
238
302
## ⚠️ Codex Adapter Runtime
239
303
240
304
- The Codex adapter talks directly to the Codex CLI through Node APIs and **must run on the server**. It is safe to import in build tooling, but gate runtime usage to environments where `process.versions.node` exists.
Copy file name to clipboardExpand all lines: packages/core/README.md
+64Lines changed: 64 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -235,6 +235,70 @@ In this workflow two reviewers (Claude, Codex) analyze the same commit in parall
235
235
236
236
---
237
237
238
+
## 🛠 Custom Tools (Claude)
239
+
240
+
The SDK provides a unified interface for creating custom tools that extend Claude's capabilities, following the Claude Agent SDK's MCP (Model Context Protocol) pattern:
const result =awaitthread.run("What's the weather in San Francisco? (37.7749, -122.4194)");
288
+
console.log(result.text);
289
+
```
290
+
291
+
**Key Features:**
292
+
-**Type-safe schemas** – Define input schemas with full TypeScript support
293
+
-**Tool name management** – Use `getToolName(server, tool)` for proper MCP naming (`mcp__{server}__{tool}`)
294
+
-**Selective permissions** – Control which tools Claude can use via `allowedTools`
295
+
-**Streaming support** – Custom tools work seamlessly with `runStreamed()`
296
+
-**Claude native** – Use Claude's native `tool()` and `createSdkMcpServer()` directly if preferred
297
+
298
+
See `examples/src/claude-custom-tools.test.ts` for comprehensive examples including calculator, formatter, and multi-tool workflows.
299
+
300
+
---
301
+
238
302
## ⚠️ Codex Adapter Runtime
239
303
240
304
- The Codex adapter talks directly to the Codex CLI through Node APIs and **must run on the server**. It is safe to import in build tooling, but gate runtime usage to environments where `process.versions.node` exists.
0 commit comments