タイムラインに戻る

8 ファイル変更 +10 -8

この更新の概要

Windows環境におけるPowerShellとコマンドプロンプトの判別方法が、具体的なエラーメッセージと共に詳しく追記されました。ルーチンの実行APIにおけるtextフィールドの仕様が明確化され、JSONなどの構造化データもリテラル文字列として扱われる点が強調されています。Agent SDKのドキュメントではコード例がPythonからTypeScriptに修正され、Gitワークツリーに関する記述も簡略化されました。プラグインの検索ツールにおいて、古いバージョンのディレクトリをスキップする仕様が新たに追加されています。

agent-sdk/overview +2 -2

コード例で使用されていたファイル名がauth.pyからauth.tsに変更され、TypeScript環境に合わせた記述になりました。

@@ -29,7 +29,7 @@ asyncio.run(main())
import { query } from "@anthropic-ai/claude-agent-sdk";
for await (const message of query({
prompt: "Find and fix the bug in auth.py",
prompt: "Find and fix the bug in auth.ts",
options: { allowedTools: ["Read", "Edit", "Bash"] }
})) {
console.log(message); // Claude reads the file, finds the bug, edits it
@@ -431,7 +431,7 @@ while (response.stop_reason === "tool_use") {
}
// Agent SDK: Claude handles tools autonomously
for await (const message of query({ prompt: "Fix the bug in auth.py" })) {
for await (const message of query({ prompt: "Fix the bug in auth.ts" })) {
console.log(message);
}
```
agent-sdk/typescript +1 -1

git worktreeの作成に関する戻り値の説明が、より簡潔な表現に修正されました。

@@ -2070,7 +2070,7 @@ type EnterWorktreeOutput = {
};
```
Returns information about the created git worktree.
Returns information about the git worktree.
## Permission Types
overview +1 -1

PowerShellとコマンドプロンプトで発生する異なるエラーメッセージに基づき、使用中のシェルを特定する方法が詳しく追記されました。

@@ -35,7 +35,7 @@ irm https://claude.ai/install.ps1 | iex
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```
If you see `The token '&&' is not a valid statement separator`, you're in PowerShell, not CMD. Use the PowerShell command above instead. Your prompt shows `PS C:\` when you're in PowerShell.
If you see `The token '&&' is not a valid statement separator`, you're in PowerShell, not CMD. If you see `'irm' is not recognized as an internal or external command`, you're in CMD, not PowerShell. Your prompt shows `PS C:\` when you're in PowerShell and `C:\` without the `PS` when you're in CMD.
**Native Windows setups require [Git for Windows](https://git-scm.com/downloads/win).** Install it first if you don't have it. WSL setups do not need it.
plugins-reference +2 -0

GlobやGrepツールが検索時に古いバージョンのディレクトリをスキップし、古いコードが含まれないようになったことが明記されました。

@@ -500,6 +500,8 @@ For security and verification purposes, Claude Code copies *marketplace* plugins
Each installed version is a separate directory in the cache. When you update or uninstall a plugin, the previous version directory is marked as orphaned and removed automatically 7 days later. The grace period lets concurrent Claude Code sessions that already loaded the old version keep running without errors.
Claude's Glob and Grep tools skip orphaned version directories during searches, so file results don't include outdated plugin code.
### Path traversal limitations
Installed plugins cannot reference files outside their directory. Paths that traverse outside the plugin root (such as `../shared-utils`) will not work after installation because those external files are not copied to the cache.
quickstart +1 -1

Windowsでのセットアップ時にシェルを間違えた際のエラー内容と、プロンプト表示による見分け方の解説が強化されました。

@@ -383,7 +383,7 @@ To install Claude Code, use one of the following methods:
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```
If you see `The token '&&' is not a valid statement separator`, you're in PowerShell, not CMD. Use the PowerShell command above instead. Your prompt shows `PS C:\` when you're in PowerShell.
If you see `The token '&&' is not a valid statement separator`, you're in PowerShell, not CMD. If you see `'irm' is not recognized as an internal or external command`, you're in CMD, not PowerShell. Your prompt shows `PS C:\` when you're in PowerShell and `C:\` without the `PS` when you're in CMD.
**Native Windows setups require [Git for Windows](https://git-scm.com/downloads/win).** Install it first if you don't have it. WSL setups do not need it.
routines +1 -1

/fireエンドポイントのtextフィールドが自由形式のテキストとして扱われ、構造化データもパースされずに渡される仕様が追記されました。

@@ -125,7 +125,7 @@ Each routine has its own token, scoped to triggering that routine only. To rotat
#### Trigger a routine
Send a POST request to the `/fire` endpoint with the bearer token in the `Authorization` header. The request body accepts an optional `text` field that's appended to the routine's configured prompt as a one-shot user turn. Use `text` to pass context like an alert body or a failing log.
Send a POST request to the `/fire` endpoint with the bearer token in the `Authorization` header. The request body accepts an optional `text` field for run-specific context such as an alert body or a failing log, passed to the routine alongside its saved prompt. The value is freeform text and is not parsed: if you send JSON or another structured payload, the routine receives it as a literal string.
The example below triggers a routine from a shell:
setup +1 -1

PowerShellとCMDの誤用を防ぐため、それぞれで発生する特有のエラーメッセージと比較方法が追加されました。

@@ -54,7 +54,7 @@ irm https://claude.ai/install.ps1 | iex
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```
If you see `The token '&&' is not a valid statement separator`, you're in PowerShell, not CMD. Use the PowerShell command above instead. Your prompt shows `PS C:\` when you're in PowerShell.
If you see `The token '&&' is not a valid statement separator`, you're in PowerShell, not CMD. If you see `'irm' is not recognized as an internal or external command`, you're in CMD, not PowerShell. Your prompt shows `PS C:\` when you're in PowerShell and `C:\` without the `PS` when you're in CMD.
**Native Windows setups require [Git for Windows](https://git-scm.com/downloads/win).** Install it first if you don't have it. WSL setups do not need it.
web-scheduled-tasks +1 -1

ルーチン実行時のtextフィールドに渡すコンテキストの扱いについて、パースされないリテラル文字列である旨の説明が更新されました。

@@ -125,7 +125,7 @@ Each routine has its own token, scoped to triggering that routine only. To rotat
#### Trigger a routine
Send a POST request to the `/fire` endpoint with the bearer token in the `Authorization` header. The request body accepts an optional `text` field that's appended to the routine's configured prompt as a one-shot user turn. Use `text` to pass context like an alert body or a failing log.
Send a POST request to the `/fire` endpoint with the bearer token in the `Authorization` header. The request body accepts an optional `text` field for run-specific context such as an alert body or a failing log, passed to the routine alongside its saved prompt. The value is freeform text and is not parsed: if you send JSON or another structured payload, the routine receives it as a literal string.
The example below triggers a routine from a shell: