claude_agent 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 962eff5c1e28589e347c1096e8c9683714b58bc95d56f281256580311bf0b87f
+  data.tar.gz: e482f60ed6579f9b364e2947b970fca1eaf35c6eec02e5669d557b9c5caf15bc
+SHA512:
+  metadata.gz: 03fc463581c3dc92b0f3d121e7f59f252b746e0a049f4eb505ef14938799de397f4cb64cd01fca09946c8be38b767205792a06f51cfa968abd880eebc2b7d79c
+  data.tar.gz: a3407945fe4b87957c898ca2872f869b62cd520db7afbf76602aa5105febcb2a95dc5a66131b68ad0254b8b7f922ecc387394f96bd78ac9da2227443f3cb2a33

data/.claude/commands/spec/complete.md

@@ -0,0 +1,105 @@
+---
+description: Implement missing Ruby SDK features identified in SPEC.md to achieve full parity with TypeScript/Python SDKs
+allowed-tools: Bash, Read, Glob, Grep, Write, Edit, TodoWrite, Task, AskUserQuestion, EnterPlanMode
+---
+
+# Complete SDK Feature Parity
+
+You are implementing missing features in the Ruby SDK to achieve full parity with the official TypeScript and Python Claude Agent SDKs.
+
+## Step 1: Identify Missing Features
+
+Read SPEC.md and identify all features where the Ruby SDK shows ❌ (not implemented):
+
+```
+Read SPEC.md
+```
+
+Create a prioritized list of missing features:
+1. **High Priority** - Features implemented in BOTH TypeScript and Python SDKs
+2. **Medium Priority** - Features only in TypeScript SDK (Python also missing)
+3. **Low Priority** - TypeScript-only features that may be JS-specific
+
+Use TodoWrite to track the features to implement.
+
+## Step 2: Research Each Feature
+
+For each missing feature, gather complete context before planning:
+
+### 2a. Official Documentation
+
+Use the `claude-code-guide` agent to understand the feature's intended behavior:
+
+```
+Task(subagent_type: "claude-code-guide", prompt: "How does [feature] work in the Claude Agent SDK? What are all the options, behaviors, and edge cases?")
+```
+
+### 2b. TypeScript Implementation
+
+Read the TypeScript type definitions to understand the API surface:
+- `vendor/claude-agent-sdk-npm/sdk.d.ts`
+
+### 2c. Python Implementation (if available)
+
+If Python has the feature, read their implementation for patterns:
+- `vendor/claude-agent-sdk-python/src/claude_agent_sdk/types.py`
+- `vendor/claude-agent-sdk-python/src/claude_agent_sdk/_internal/`
+
+## Step 3: Clarify Requirements
+
+Use AskUserQuestion to resolve any ambiguities:
+
+- Implementation approach choices
+- Ruby-specific design decisions
+- Whether certain features should be skipped (e.g., JS-specific)
+- Priority ordering if time-constrained
+
+## Step 4: Enter Plan Mode
+
+Enter plan mode to design the implementation:
+
+```
+EnterPlanMode
+```
+
+The plan should include:
+- Which files to create or modify
+- Data structures (use `Data.define` for immutable types)
+- Public API design
+- Test coverage requirements
+- Any breaking changes or deprecations
+
+## Step 5: Implement Features
+
+After plan approval, implement each feature:
+
+1. Add types/data structures
+2. Update Options if new configuration needed
+3. Implement core functionality
+4. Add CLI argument mapping (if applicable)
+5. Update RBS type signatures in `sig/` directory
+6. Write unit tests in `test/claude_agent/`
+7. Write integration tests in `test/integration/` for features that interact with CLI/API
+8. Update SPEC.md to mark feature as ✅
+
+### Testing Requirements
+
+- **Unit tests** - For all new types, data structures, and internal logic
+- **Integration tests** - Required for anything that:
+  - Spawns the CLI subprocess
+  - Sends/receives messages via the control protocol
+  - Interacts with MCP servers
+  - Uses file checkpointing or session management
+
+## Step 6: Update Specification
+
+After implementing features, run `/spec:update` to refresh SPEC.md with the new implementation status.
+
+## Output
+
+Provide a summary of:
+- Features implemented
+- Any features skipped (with reasons)
+- Breaking changes introduced
+- Test coverage added
+- Remaining gaps (if any)

data/.claude/commands/spec/update.md

@@ -0,0 +1,95 @@
+---
+description: Update SPEC.md with latest feature parity comparison across TypeScript, Python, and Ruby SDKs
+allowed-tools: Bash, Read, Glob, Grep, Write, Edit, TodoWrite, Task
+---
+
+# Update SDK Specification Document
+
+You are updating the SPEC.md file to reflect the current feature parity between the TypeScript, Python, and Ruby Claude Agent SDKs.
+
+## Step 1: Update Reference SDKs
+
+First, ensure the reference SDKs are up to date:
+
+```bash
+bin/update-reference-sdks
+```
+
+This clones/updates:
+- Python SDK from GitHub → `vendor/claude-agent-sdk-python`
+- TypeScript SDK from npm → `vendor/claude-agent-sdk-npm`
+
+## Step 2: Research Official Documentation
+
+Use the `claude-code-guide` agent to check for any new or updated SDK features:
+
+```
+Task(subagent_type: "claude-code-guide", prompt: "What are all the features and options in the Claude Agent SDK? Include configuration options, hooks, permissions, MCP support, and control protocol methods.")
+```
+
+This helps catch features that may be documented but not yet in the SDK source files.
+
+## Step 3: Analyze All Three SDKs
+
+Read and compare the following files:
+
+### TypeScript SDK (Primary Reference)
+- `vendor/claude-agent-sdk-npm/sdk.d.ts` - Complete API surface with all types
+
+### Python SDK
+- `vendor/claude-agent-sdk-python/src/claude_agent_sdk/types.py` - Type definitions
+
+### Ruby SDK (This Repository)
+Key files to check:
+- `lib/claude_agent/options.rb` - Configuration options
+- `lib/claude_agent/messages.rb` - Message types
+- `lib/claude_agent/content_blocks.rb` - Content block types
+- `lib/claude_agent/types.rb` - Additional types
+- `lib/claude_agent/hooks.rb` - Hook types
+- `lib/claude_agent/permissions.rb` - Permission types
+- `lib/claude_agent/control_protocol.rb` - Control protocol
+- `lib/claude_agent/sandbox_settings.rb` - Sandbox config
+- `lib/claude_agent/mcp/server.rb` - MCP server
+- `lib/claude_agent/mcp/tool.rb` - MCP tools
+- `lib/claude_agent/client.rb` - Client class
+- `lib/claude_agent/errors.rb` - Error types
+
+## Step 4: Update SPEC.md
+
+Update the existing SPEC.md file with:
+
+1. **Reference Versions** - Update TypeScript SDK version and Python SDK commit
+2. **Feature Tables** - Update all ✅/❌ markers based on current implementations
+3. **New Features** - Add any new features found in the TypeScript SDK
+4. **Removed Features** - Remove any deprecated features
+
+### Categories to Compare
+
+1. Options/Configuration
+2. Message Types
+3. Content Blocks
+4. Control Protocol
+5. Hooks
+6. Permissions
+7. MCP Support
+8. Sessions
+9. Subagents
+10. Sandbox Settings
+11. Error Handling
+12. Client API
+
+## Guidelines
+
+- **Be thorough** - Check every field and option in each SDK
+- **TypeScript is authoritative** - The TypeScript sdk.d.ts is the most complete reference
+- **Preserve format** - Keep the existing table structure and markdown formatting
+- **Update versions** - Always update the reference version info at the top
+- **Note changes** - If significant changes are found, mention them after updating
+
+## Output
+
+After updating SPEC.md, provide a brief summary of:
+- SDK versions checked
+- Any new features added to the spec
+- Any features removed from the spec
+- Any notable gaps in the Ruby SDK