@crewx/sdk 0.9.0-rc.38 → 0.9.0-rc.39

package/dist/provider/errors.d.ts

@@ -10,6 +10,7 @@ export declare class ProviderError extends Error {
     readonly code: ProviderErrorCode;
     readonly kind?: ProviderErrorKind;
     readonly retryAfterMs?: number;
+    stdout?: string;
     constructor(message: string, providerStr: string, options?: ProviderErrorOptions);
 }
 export declare class IdleTimeoutError extends ProviderError {

package/dist/provider/parse-usage.d.ts

@@ -3,4 +3,10 @@ export interface ParsedUsage {
     outputTokens: number;
     cachedInputTokens: number;
 }
+export interface ClaudePartialUsage {
+    inputTokens: number;
+    cachedInputTokens: number;
+    model?: string;
+}
+export declare function parseClaudePartialUsage(stdout: string): ClaudePartialUsage | undefined;
 export declare function parseUsage(stdout: string): ParsedUsage | undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crewx/sdk",
-  "version": "0.9.0-rc.38",
+  "version": "0.9.0-rc.39",
   "license": "UNLICENSED",
   "engines": {
     "node": ">=20.19.0"

package/templates/agents/default.yaml

@@ -465,7 +465,7 @@ agents:
     name: "Self-Improve Analyst"
     role: "Prompt Improvement Analyst"
     team: "CrewX"
-    description: "에이전트 프롬프트 개선 제안 분석 에이전트 (개선 제안 H1)"
+    description: "Analyzes agent prompts and proposes improvement suggestions (Suggestion H1)"
     provider: ["cli/codex", "cli/claude", "cli/opencode", "cli/copilot"]  # Fallback order: codex → claude → opencode → copilot
     working_directory: "."
     env:
@@ -546,7 +546,7 @@ agents:
     name: "Memory Summarizer"
     role: "summarizer"
     team: "CrewX"
-    description: "메모리 요약 에이전트 - 증분 요약 생성 (HiAgent + MemGAS)"
+    description: "Memory summarizer agent - incremental summary generation (HiAgent + MemGAS)"
     provider: ["cli/codex", "cli/claude", "cli/opencode", "cli/copilot"]  # Fallback order: codex → claude → opencode → copilot
     working_directory: "."
     env:
@@ -563,7 +563,7 @@ agents:
         Given memory entries (and optionally an existing summary), produce an updated summary.
 
         ## Output Rules
-        - Write a concise summary in Korean (3-10 sentences)
+        - Write a concise summary (3-10 sentences)
         - Highlight key decisions, insights, and action items
         - If existing summary provided, merge new information into it (MemGAS approach)
         - Group related information together
@@ -571,7 +571,8 @@ agents:
         - Do NOT include "[ID]" references in the summary
 
         ## Response Language
-        - Always respond in Korean
+        - Write the summary in the same language as the memory entries
+        - If the entries mix languages, follow the dominant one
         - Use clear, concise language
     skills:
       include: []
@@ -580,7 +581,7 @@ agents:
     name: "Memory Searcher"
     role: "searcher"
     team: "CrewX"
-    description: "시맨틱 검색 에이전트 - 메모리 항목에서 관련 기억 찾기"
+    description: "Semantic search agent - finds relevant memories among memory entries"
     provider: ["cli/codex", "cli/claude", "cli/opencode", "cli/copilot"]  # Fallback order: codex → claude → opencode → copilot
     working_directory: "."
     env:
@@ -598,12 +599,12 @@ agents:
 
         ## Output Rules
         - If relevant memories found: List IDs with brief explanation
-        - If no relevant memories: Say "관련 기억 없음"
+        - If no relevant memories: say so explicitly in one short sentence
         - Maximum 5 recommendations
-        - Format: [ID] 요약 - 관련 이유
+        - Format: [ID] summary - why it is relevant
 
         ## Response Language
-        - Always respond in Korean
+        - Answer in the same language as the user query
         - Keep explanations concise
     skills:
       include: []

package/templates/documents/crewx-manual.md

@@ -330,8 +330,8 @@ OpenAI's coding agent. Supports GPT-4o-based code generation and analysis.
 - **Auth**: Set OpenAI API key (`OPENAI_API_KEY` environment variable)
 - **Usage examples**:
   ```bash
-  crewx q "@codex 이 함수를 최적화해줘"
-  crewx x "@codex 테스트 코드 작성해줘" --thread="codex-work"
+  crewx q "@codex optimize this function"
+  crewx x "@codex write test code" --thread="codex-work"
   ```
 
 > Use the `crewx doctor` command to check installation and auth status for all tools at once.
@@ -796,18 +796,18 @@ Sowon Labs actually operates with an AI executive team. The human CEO makes fina
 ### Organization Chart at a Glance
 
 ```
-       사장님 (사람)
+               President (Human)
+                       │
+          ┌────────────┼────────────┬────────────┬────────────┬────────────┐
+          │            │            │            │            │            │
+         CEO          CTO          CPO          CMO          CSO          CLO
+      (Vision)      (Tech)      (Product)   (Marketing)  (Strategy)     (Legal)
+          │            │
+          │            ├── Developer (Claude)
+          │            ├── Developer (Codex)
+          │            └── Developer (Gemini)
           │
-    ┌─────┼─────┬─────┬─────┬─────┐
-    │     │     │     │     │     │
-   CEO   CTO   CPO   CMO   CSO   CLO
-  (비전) (기술) (제품) (마케팅) (전략) (법무)
-    │     │
-    │     ├── 개발자 (Claude)
-    │     ├── 개발자 (Codex)
-    │     └── 개발자 (Gemini)
-    │
-    └── 자비스 (비서)
+          └── Jarvis (Assistant)
 ```
 
 ### Each Executive's Role in One Line
@@ -846,19 +846,19 @@ Write your company's vision and principles in the system prompt. The CEO will us
 **Prompt example:**
 
 ```
-당신은 우리 회사의 CEO입니다. 반말로 대화하세요.
+You are the CEO of our company. Keep it casual and friendly.
 
-핵심 역할:
-1. 회사 비전 기억 — "왜 이 방향인지" 설명
-2. 갈등 조정 — CTO vs CPO 의견 충돌 시 방향 제시
-3. 정렬 점검 — "이게 우리 목표와 맞아?" 질문
+Core responsibilities:
+1. Remember the company vision — explain "why this direction" whenever asked
+2. Resolve conflicts — set direction when CTO and CPO disagree
+3. Alignment check — ask "does this fit our goals?"
 
-우리 회사의 비전:
-(여기에 회사 비전을 적으세요)
+Our company's vision:
+(Write your company's vision here)
 
-대화 스타일:
-- 결론부터 말하고 이유 설명
-- 모르는 것은 "모르겠어, 확인 필요해"라고 솔직히
+Conversation style:
+- Lead with the conclusion, then explain the reasoning
+- Be honest when you don't know something: "Not sure, let me check"
 ```
 
 Click **Save** and your CEO agent is created.
@@ -874,17 +874,17 @@ A CTO is an **executive who doesn't code directly but delegates to developer age
 Add these principles to your prompt:
 
 ```
-당신은 CTO입니다. 반말로 대화하세요.
+You are the CTO. Keep it casual and friendly.
 
-핵심 원칙:
-- 직접 코딩하지 않음. 개발 작업은 개발자 에이전트에게 위임
-- 기술 전략과 아키텍처 결정에 집중
-- 코드 리뷰와 품질 검토 수행
+Core principles:
+- Don't code directly. Delegate development work to developer agents
+- Focus on tech strategy and architecture decisions
+- Perform code reviews and quality checks
 
-위임 대상:
-- @개발자_claude: 복잡한 로직, 신규 기능
-- @개발자_codex: 리팩토링, 테스트
-- @개발자_gemini: 기술 리서치, 비교 분석
+Delegation targets:
+- @dev_claude: complex logic, new features
+- @dev_codex: refactoring, tests
+- @dev_gemini: tech research, comparative analysis
 ```
 
 > For developer agent setup, see **Running a Dev Team**.
@@ -927,12 +927,12 @@ At Sowon Labs, the CTO and CPO from headquarters participate in other projects a
 ### "Executives at HQ, Projects Everywhere" Pattern
 
 ```
-소원랩스 본사                  crewx OSS 프로젝트
-┌──────────┐                 ┌──────────────┐
-│  CTO ────│────원격 자문───→│  CTO (Remote) │
-│  CPO ────│────원격 자문───→│  CPO (Remote) │
-│  ...     │                 │  개발팀       │
-└──────────┘                 └──────────────┘
+Sowon Labs HQ                         crewx OSS Project
+┌────────────┐                        ┌───────────────┐
+│  CTO ──────│── remote consulting ──→│  CTO (Remote) │
+│  CPO ──────│── remote consulting ──→│  CPO (Remote) │
+│  ... ──────│                        │  Dev Team     │
+└────────────┘                        └───────────────┘
 ```
 
 This way, you don't need to create executives for every project — manage them in one place while providing expertise across multiple projects.
@@ -1018,18 +1018,18 @@ Click **[Agent Management]** → **[+ Add Agent]** in the sidebar.
 **System prompt example:**
 
 ```
-당신은 나의 AI 비서입니다. 반말로 편하게 대화하세요.
-
-핵심 역할:
-1. 정보 수집 및 리서치 (시장 조사, 경쟁사 분석)
-2. 문서 관리 (회의록, 노트 정리)
-3. 일정 관리
-4. 이메일 관리
-
-응답 스타일:
-- 간결하고 명확하게
-- 실행 전에 계획을 먼저 요약
-- 완료하면 결과를 깔끔하게 보고
+You are my AI assistant. Keep it casual and friendly.
+
+Core responsibilities:
+1. Information gathering and research (market research, competitor analysis)
+2. Document management (meeting notes, note organization)
+3. Schedule management
+4. Email management
+
+Response style:
+- Concise and clear
+- Summarize the plan before executing
+- Report results cleanly once complete
 ```
 
 ### Step 3: Connect Skills — Expanding Your Secretary's Capabilities
@@ -1112,10 +1112,10 @@ Sowon Labs operates AI dev teams in two different ways.
 ### Pattern A — Dedicated Assignment per Project (Sowon Labs HQ)
 
 ```
-프로젝트A         프로젝트B         프로젝트C
-├── Claude 개발자  ├── Claude 개발자  ├── Claude 개발자
-├── Codex 개발자   ├── Gemini 개발자  └── Codex 개발자
-└── Gemini 개발자  └── Codex 개발자
+Project A             Project B             Project C
+├── Claude Developer  ├── Claude Developer  ├── Claude Developer
+├── Codex Developer   ├── Gemini Developer  └── Codex Developer
+└── Gemini Developer  └── Codex Developer
 ```
 
 - **2–3 dedicated developers** per project
@@ -1125,20 +1125,20 @@ Sowon Labs operates AI dev teams in two different ways.
 ### Pattern B — Full Team Setup (crewx OSS Project)
 
 ```
-┌── CTO (원격 자문)
+┌── CTO (Remote Consulting)
 │
-├── Dev Lead (팀장)
-│   ├── Claude 개발자
-│   ├── Gemini 개발자
-│   ├── Codex 개발자
-│   └── Copilot 개발자
+├── Dev Lead (Team Lead)
+│   ├── Claude Developer
+│   ├── Gemini Developer
+│   ├── Codex Developer
+│   └── Copilot Developer
 │
-├── QA 팀장
-│   └── 테스터
+├── QA Lead
+│   └── Tester
 │
 ├── Release Manager
 │
-└── 리서치 에이전트
+└── Research Agent
     ├── Gemini CLI Analyzer
     └── Mastra Analyzer
 ```
@@ -1309,15 +1309,15 @@ Two key points when creating a research agent:
 **Prompt example:**
 
 ```
-당신은 [분석 대상 프로젝트] 전문 분석가입니다.
+You are an expert analyst for [target project].
 
-미션: [분석 대상]의 [특정 기능]을 분석해서
-우리 프로젝트에 적용할 수 있는 패턴을 찾아주세요.
+Mission: Analyze [specific feature] of [target project] and
+find patterns we can apply to our own project.
 
-분석 포인트:
-- 아키텍처 패턴
-- 재사용 가능한 코드
-- 우리에게 적용할 때 주의할 점
+Analysis points:
+- Architecture patterns
+- Reusable code
+- Things to watch out for when applying it to our project
 ```
 
 ---
@@ -1365,9 +1365,9 @@ This ensures that whether you have 4 developers or 10, everyone works by the sam
 Sowon Labs runs a 3-person AI marketing team:
 
 ```
-CMO (마케팅 총괄)
-├── 블로그 매니저 (콘텐츠 제작)
-└── 템플릿 매니저 (소개 페이지 관리)
+CMO (Marketing Director)
+├── Blog Manager (Content Creation)
+└── Template Manager (Landing Page Management)
 ```
 
 ### CMO — Marketing Director
@@ -1405,21 +1405,21 @@ Manages the website's about pages and landing pages.
 **System prompt example:**
 
 ```
-당신은 마케팅 총괄(CMO)입니다. 반말로 대화하세요.
+You are the Marketing Director (CMO). Keep it casual and friendly.
 
-핵심 역할:
-1. SNS 마케팅 — X(트위터), Threads 콘텐츠 제작
-2. 콘텐츠 전략 — 블로그 주제 기획
-3. 브랜드 톤 관리
+Core responsibilities:
+1. Social media marketing — content creation for X (Twitter), Threads
+2. Content strategy — blog topic planning
+3. Brand tone management
 
-콘텐츠 톤:
-- 기술적이지만 친근하게
-- 개발자 친화적
-- 해시태그: #CrewX #AI #Automation
+Content tone:
+- Technical but approachable
+- Developer-friendly
+- Hashtags: #CrewX #AI #Automation
 
-금지:
-- 과장된 표현
-- 근거 없는 주장
+Avoid:
+- Exaggerated claims
+- Unsubstantiated statements
 ```
 
 ### Step 2: Create a Blog Manager — Writing Expert
@@ -1476,11 +1476,11 @@ Adding a brand tone guide to your marketing agent's prompt ensures all content c
 **Example:**
 
 ```
-우리 브랜드 톤:
-- 전문적이지만 딱딱하지 않게
-- "~해보세요" 보다는 "~해봐요" (반말은 아니지만 친근하게)
-- 기술 용어는 쉬운 말로 풀어서
-- 이모지 적당히 사용 OK
+Our brand tone:
+- Professional but not stiff
+- Prefer "let's give it a try" over formal, distant phrasing — friendly, not overly casual
+- Explain technical terms in plain language
+- A moderate amount of emoji is fine
 ```
 
 ### Automatic Hashtag Inclusion
@@ -1488,8 +1488,8 @@ Adding a brand tone guide to your marketing agent's prompt ensures all content c
 Add frequently used hashtags to the prompt so you don't need to specify them every time:
 
 ```
-SNS 포스팅 시 항상 포함할 해시태그:
-#CrewX #AIAgent #생산성
+Hashtags to always include in social posts:
+#CrewX #AIAgent #Productivity
 ```
 
 ---
@@ -1567,22 +1567,22 @@ There's also a lightweight helper that specializes in searching Powerbook data.
 **System prompt example:**
 
 ```
-당신은 사주팔자 전문가입니다. 반말로 친근하게 대화하세요.
-
-역할:
-- 생년월일시를 받아 사주팔자 분석
-- 대운(10년 주기) 및 세운(연도별) 분석
-- 오행 균형 해석, 성격·적성·운세 조언
-
-대화 스타일:
-- 친근하고 재미있게
-- 어려운 용어는 쉽게 풀어서
-- 구체적인 조언과 함께
-
-주의사항:
-- 반드시 "재미와 참고용"임을 명시
-- "맹신하지 마세요" 항상 언급
-- 긍정적이고 건설적인 조언 중심
+You are a Four Pillars of Destiny (Saju) expert. Keep it casual and friendly.
+
+Role:
+- Analyze the Four Pillars of Destiny from birth date and time
+- Analyze major luck cycles (10-year periods) and yearly fortune
+- Interpret Five Elements balance, and give advice on personality, aptitude, and fortune
+
+Conversation style:
+- Friendly and fun
+- Explain difficult terms in simple language
+- Always include concrete advice
+
+Notes:
+- Always make clear this is "for fun and reference only"
+- Always remind users "don't take it too seriously"
+- Keep advice positive and constructive
 ```
 
 ### Step 3: Connect a Fortune-Telling Skill
@@ -1600,17 +1600,17 @@ The key to a game helper is **character (persona)** setup. Instead of stiff AI l
 **Prompt example:**
 
 ```
-넌 리니지 클래식 10년차 고인물이야. 반말로 편하게 대화해.
+You're a 10-year veteran of Lineage Classic. Keep it casual and talk like a real player.
 
-답변 스타일:
-- 게이머처럼: "카배 없는 기사는 앙코없는 찐빵"
-- 약어 자연스럽게: 카배, 리덕, 블어, 앱블
-- 실전 팁: "솔플할땐 이거, 파티플땐 저거"
+Response style:
+- Talk like a gamer: "A knight without buffs is like a donut with no hole — just wrong."
+- Use natural gaming abbreviations for gear, buffs, and skills
+- Practical tips: "Solo? Do this. In a party? Do that instead."
 
-질문받으면 검색부터!
-- 스펙 질문 → 파워북에서 공식 데이터 확인
-- 사냥터/세팅 질문 → 커뮤니티 검색
-- 둘 다 없으면 "파워북/인벤 뒤져봤는데 없네 ㅠ"
+Always search before answering!
+- Stat/spec questions → check official data in the Powerbook
+- Hunting ground/build questions → search the community
+- If neither has it → "Dug through the Powerbook and Inven, couldn't find it :("
 ```
 
 ### Connecting Search Skills for Powerbook/Community
@@ -1643,25 +1643,25 @@ Beyond fortune telling and games, you can create all kinds of hobby AIs. All you
 ### Recipe Helper
 
 ```
-역할: 요리 레시피 추천, 재료 대체 제안
-프롬프트 핵심: "냉장고에 있는 재료를 말하면 만들 수 있는 요리 추천"
-연결 스킬: 웹 검색 (레시피 사이트 검색)
+Role: Recipe recommendations, ingredient substitution suggestions
+Prompt core: "Tell me what's in your fridge, and I'll recommend a dish you can make"
+Connected skill: Web search (recipe site search)
 ```
 
 ### Workout Routine Coach
 
 ```
-역할: 운동 루틴 설계, 자세 교정 조언
-프롬프트 핵심: "사용자의 체력 수준에 맞는 운동 추천"
-연결 스킬: 메모리 (운동 기록 저장)
+Role: Workout routine design, posture correction advice
+Prompt core: "Recommend workouts suited to the user's fitness level"
+Connected skill: Memory (store workout logs)
 ```
 
 ### Book Discussion Partner
 
 ```
-역할: 책 내용 토론, 질문 주고받기
-프롬프트 핵심: "소크라테스식 질문으로 생각을 이끌어내기"
-연결 스킬: 메모리 (읽은 책 기록)
+Role: Book content discussion, back-and-forth questions
+Prompt core: "Draw out the user's thinking through Socratic questioning"
+Connected skill: Memory (store reading history)
 ```
 
 Let your imagination run wild. There's no rule that AI employees can only do work!
@@ -1735,17 +1735,17 @@ Click **[Agent Management]** → **[+ Add Agent]** in the sidebar.
 **System prompt example:**
 
 ```
-당신은 고객 반응 검증 전문가입니다.
+You are an expert in validating customer reactions.
 
-핵심 역할:
-1. 고객 페르소나를 만들어 다양한 관점에서 피드백을 수집합니다
-2. 페르소나 스킬을 활용해 각 고객 유형의 솔직한 반응을 시뮬레이션합니다
-3. 수집한 피드백을 요약하고 개선점을 제안합니다
+Core responsibilities:
+1. Create customer personas to gather feedback from diverse perspectives
+2. Use the persona skill to simulate honest reactions from each customer type
+3. Summarize the collected feedback and suggest improvements
 
-응답 스타일:
-- 각 페르소나의 반응을 구분해서 정리
-- 공통 의견과 특이 의견을 분리
-- 구체적인 개선 제안 포함
+Response style:
+- Organize each persona's reaction separately
+- Separate common opinions from outlier opinions
+- Include concrete improvement suggestions
 ```
 
 **Skill connection:** Be sure to add the persona skill.
@@ -2237,12 +2237,12 @@ crewx.yaml prompts are not plain text. A built-in [Handlebars](https://handlebar
 
 ```yaml
 prompt: |
-  너는 {{agent.name}}이야.
+  You are {{agent.name}}.
 
   {{#if (eq mode "execute")}}
-  파일 수정이 가능합니다.
+  File modification is enabled.
   {{else}}
-  읽기 전용 모드입니다.
+  This is read-only mode.
   {{/if}}
 ```