2026-02-10 11:34:08 +00:00
|
|
|
|
<div align="center">
|
2026-03-12 08:10:29 +00:00
|
|
|
|
<img src="assets/logo.webp" alt="PicoClaw" width="512">
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
<h1>PicoClaw: Go で書かれた超効率 AI アシスタント</h1>
|
|
|
|
|
|
|
2026-02-15 14:56:13 +00:00
|
|
|
|
<h3>$10 ハードウェア · 10MB RAM · 1秒起動 · 行くぜ、シャコ!</h3>
|
2026-02-10 11:34:08 +00:00
|
|
|
|
<h3></h3>
|
2026-03-14 09:20:49 +00:00
|
|
|
|
<p>
|
|
|
|
|
|
<img src="https://img.shields.io/badge/Go-1.21+-00ADD8?style=flat&logo=go&logoColor=white" alt="Go">
|
|
|
|
|
|
<img src="https://img.shields.io/badge/Arch-x86__64%2C%20ARM64%2C%20MIPS%2C%20RISC--V-blue" alt="Hardware">
|
|
|
|
|
|
<img src="https://img.shields.io/badge/license-MIT-green" alt="License">
|
|
|
|
|
|
<br>
|
|
|
|
|
|
<a href="https://picoclaw.io"><img src="https://img.shields.io/badge/Website-picoclaw.io-blue?style=flat&logo=google-chrome&logoColor=white" alt="Website"></a>
|
|
|
|
|
|
<a href="https://docs.picoclaw.io/"><img src="https://img.shields.io/badge/Docs-Official-007acc?style=flat&logo=read-the-docs&logoColor=white" alt="Docs"></a>
|
|
|
|
|
|
<a href="https://deepwiki.com/sipeed/picoclaw"><img src="https://img.shields.io/badge/Wiki-DeepWiki-FFA500?style=flat&logo=wikipedia&logoColor=white" alt="Wiki"></a>
|
|
|
|
|
|
<br>
|
|
|
|
|
|
<a href="https://x.com/SipeedIO"><img src="https://img.shields.io/badge/X_(Twitter)-SipeedIO-black?style=flat&logo=x&logoColor=white" alt="Twitter"></a>
|
|
|
|
|
|
<a href="./assets/wechat.png"><img src="https://img.shields.io/badge/WeChat-Group-41d56b?style=flat&logo=wechat&logoColor=white"></a>
|
|
|
|
|
|
<a href="https://discord.gg/V4sAZ9XWpN"><img src="https://img.shields.io/badge/Discord-Community-4c60eb?style=flat&logo=discord&logoColor=white" alt="Discord"></a>
|
|
|
|
|
|
</p>
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-02-19 13:23:06 +00:00
|
|
|
|
[中文](README.zh.md) | **日本語** | [Português](README.pt-br.md) | [Tiếng Việt](README.vi.md) | [Français](README.fr.md) | [English](README.md)
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
2026-03-17 12:51:07 +00:00
|
|
|
|
> **PicoClaw** は [Sipeed](https://sipeed.com) が立ち上げた独立したオープンソースプロジェクトです。完全に **Go 言語**で一から書かれており、OpenClaw、NanoBot、その他のプロジェクトのフォークではありません。
|
|
|
|
|
|
|
|
|
|
|
|
🦐 PicoClaw は [NanoBot](https://github.com/HKUDS/nanobot) にインスパイアされた超軽量パーソナル AI アシスタントです。Go でゼロからリファクタリングされ、AI エージェント自身がアーキテクチャの移行とコード最適化を推進するセルフブートストラッピングプロセスで構築されました。
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
⚡️ $10 のハードウェアで 10MB 未満の RAM で動作:OpenClaw より 99% 少ないメモリ、Mac mini より 98% 安い!
|
|
|
|
|
|
|
|
|
|
|
|
<table align="center">
|
|
|
|
|
|
<tr align="center">
|
|
|
|
|
|
<td align="center" valign="top">
|
|
|
|
|
|
<p align="center">
|
|
|
|
|
|
<img src="assets/picoclaw_mem.gif" width="360" height="240">
|
|
|
|
|
|
</p>
|
|
|
|
|
|
</td>
|
|
|
|
|
|
<td align="center" valign="top">
|
|
|
|
|
|
<p align="center">
|
|
|
|
|
|
<img src="assets/licheervnano.png" width="400" height="240">
|
|
|
|
|
|
</p>
|
|
|
|
|
|
</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
</table>
|
|
|
|
|
|
|
|
|
|
|
|
## 📢 ニュース
|
2026-02-15 14:56:13 +00:00
|
|
|
|
2026-02-09 🎉 PicoClaw リリース!$10 ハードウェアで 10MB 未満の RAM で動く AI エージェントを 1 日で構築。🦐 行くぜ、シャコ!
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
## ✨ 特徴
|
|
|
|
|
|
|
|
|
|
|
|
🪶 **超軽量**: メモリフットプリント 10MB 未満 — Clawdbot のコア機能より 99% 小さい。
|
|
|
|
|
|
|
|
|
|
|
|
💰 **最小コスト**: $10 ハードウェアで動作 — Mac mini より 98% 安い。
|
|
|
|
|
|
|
|
|
|
|
|
⚡️ **超高速**: 起動時間 400 倍高速、0.6GHz シングルコアでも 1 秒で起動。
|
|
|
|
|
|
|
2026-03-06 11:54:56 +00:00
|
|
|
|
🌍 **真のポータビリティ**: RISC-V、ARM、MIPS、x86 対応の単一バイナリ。ワンクリックで Go!
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
🤖 **AI ブートストラップ**: 自律的な Go ネイティブ実装 — コアの 95% が AI 生成、人間によるレビュー付き。
|
|
|
|
|
|
|
|
|
|
|
|
| | OpenClaw | NanoBot | **PicoClaw** |
|
|
|
|
|
|
| --- | --- | --- |--- |
|
|
|
|
|
|
| **言語** | TypeScript | Python | **Go** |
|
|
|
|
|
|
| **RAM** | >1GB |>100MB| **< 10MB** |
|
|
|
|
|
|
| **起動時間**</br>(0.8GHz コア) | >500秒 | >30秒 | **<1秒** |
|
|
|
|
|
|
| **コスト** | Mac Mini 599$ | 大半の Linux SBC </br>~50$ |**あらゆる Linux ボード**</br>**最安 10$** |
|
|
|
|
|
|
<img src="assets/compare.jpg" alt="PicoClaw" width="512">
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## 🦾 デモンストレーション
|
|
|
|
|
|
### 🛠️ スタンダードアシスタントワークフロー
|
|
|
|
|
|
<table align="center">
|
|
|
|
|
|
<tr align="center">
|
|
|
|
|
|
<th><p align="center">🧩 フルスタックエンジニア</p></th>
|
|
|
|
|
|
<th><p align="center">🗂️ ログ&計画管理</p></th>
|
|
|
|
|
|
<th><p align="center">🔎 Web 検索&学習</p></th>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td align="center"><p align="center"><img src="assets/picoclaw_code.gif" width="240" height="180"></p></td>
|
|
|
|
|
|
<td align="center"><p align="center"><img src="assets/picoclaw_memory.gif" width="240" height="180"></p></td>
|
|
|
|
|
|
<td align="center"><p align="center"><img src="assets/picoclaw_search.gif" width="240" height="180"></p></td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td align="center">開発 · デプロイ · スケール</td>
|
|
|
|
|
|
<td align="center">スケジュール · 自動化 · メモリ</td>
|
|
|
|
|
|
<td align="center">発見 · インサイト · トレンド</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
</table>
|
|
|
|
|
|
|
|
|
|
|
|
### 🐜 革新的な省フットプリントデプロイ
|
|
|
|
|
|
PicoClaw はほぼすべての Linux デバイスにデプロイできます!
|
|
|
|
|
|
|
|
|
|
|
|
- $9.9 [LicheeRV-Nano](https://www.aliexpress.com/item/1005006519668532.html) E(Ethernet) または W(WiFi6) バージョン、最小ホームアシスタントに
|
|
|
|
|
|
- $30~50 [NanoKVM](https://www.aliexpress.com/item/1005007369816019.html) または $100 [NanoKVM-Pro](https://www.aliexpress.com/item/1005010048471263.html) サーバー自動メンテナンスに
|
|
|
|
|
|
- $50 [MaixCAM](https://www.aliexpress.com/item/1005008053333693.html) または $100 [MaixCAM2](https://www.kickstarter.com/projects/zepan/maixcam2-build-your-next-gen-4k-ai-camera) スマート監視に
|
|
|
|
|
|
|
|
|
|
|
|
https://private-user-images.githubusercontent.com/83055338/547056448-e7b031ff-d6f5-4468-bcca-5726b6fecb5c.mp4
|
|
|
|
|
|
|
|
|
|
|
|
🌟 もっと多くのデプロイ事例が待っています!
|
|
|
|
|
|
|
|
|
|
|
|
## 📦 インストール
|
|
|
|
|
|
|
|
|
|
|
|
### コンパイル済みバイナリでインストール
|
|
|
|
|
|
|
|
|
|
|
|
[リリースページ](https://github.com/sipeed/picoclaw/releases) からお使いのプラットフォーム用のファームウェアをダウンロードしてください。
|
|
|
|
|
|
|
|
|
|
|
|
### ソースからインストール(最新機能、開発向け推奨)
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
git clone https://github.com/sipeed/picoclaw.git
|
|
|
|
|
|
|
|
|
|
|
|
cd picoclaw
|
|
|
|
|
|
make deps
|
|
|
|
|
|
|
|
|
|
|
|
# ビルド(インストール不要)
|
|
|
|
|
|
make build
|
|
|
|
|
|
|
|
|
|
|
|
# 複数プラットフォーム向けビルド
|
|
|
|
|
|
make build-all
|
|
|
|
|
|
|
|
|
|
|
|
# ビルドとインストール
|
|
|
|
|
|
make install
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
## 🐳 Docker Compose
|
|
|
|
|
|
|
|
|
|
|
|
Docker Compose を使えば、ローカルにインストールせずに PicoClaw を実行できます。
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
# 1. リポジトリをクローン
|
2026-02-12 16:24:52 +00:00
|
|
|
|
git clone https://github.com/sipeed/picoclaw.git
|
2026-02-10 11:34:08 +00:00
|
|
|
|
cd picoclaw
|
|
|
|
|
|
|
chore(docker): reorganize docker files and add first-run entrypoint (#812)
* chore(docker): move Dockerfile into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(docker): add entrypoint script to goreleaser Dockerfile
- entrypoint.sh: on first run (config and workspace both absent) runs
picoclaw onboard then exits for the user to configure; subsequent
starts exec picoclaw gateway directly
- Dockerfile.goreleaser: copy and use entrypoint.sh, run as root
- .goreleaser.yaml: update dockerfile path, add entrypoint.sh to
extra_files so it is included in the docker build context
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore(docker): update docker-compose to use pre-built image and bind mount
- Use docker.io/sipeed/picoclaw:latest instead of building locally
- Replace named volume with bind mount ./data:/root/.picoclaw
- Move docker-compose.yml into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: update Docker Compose section to reflect new docker/ layout
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow: first run generates docker/data/config.json,
container exits, user edits config, then restarts
- Replace "Rebuild" section with "Update" (docker pull) since the
compose file now uses the pre-built sipeed/picoclaw image
- Apply same changes to README.zh.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(docker): use restart: on-failure to prevent restart after first-run setup
unless-stopped restarts the container regardless of exit code, causing
an infinite loop when entrypoint exits 0 after the initial onboard.
on-failure only restarts on non-zero exit (i.e. crashes), so the
container stays stopped after setup until the user restarts it manually.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: sync Docker Compose section across all language READMEs
Apply the same updates as the English/Chinese READMEs:
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow to first-run auto-config pattern
- Replace build/rebuild section with update via docker pull
- Affected: README.fr.md, README.ja.md, README.pt-br.md, README.vi.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-27 02:10:17 +00:00
|
|
|
|
# 2. 初回起動 — docker/data/config.json を自動生成して終了
|
|
|
|
|
|
docker compose -f docker/docker-compose.yml --profile gateway up
|
|
|
|
|
|
# コンテナが "First-run setup complete." を表示して停止します。
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
chore(docker): reorganize docker files and add first-run entrypoint (#812)
* chore(docker): move Dockerfile into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(docker): add entrypoint script to goreleaser Dockerfile
- entrypoint.sh: on first run (config and workspace both absent) runs
picoclaw onboard then exits for the user to configure; subsequent
starts exec picoclaw gateway directly
- Dockerfile.goreleaser: copy and use entrypoint.sh, run as root
- .goreleaser.yaml: update dockerfile path, add entrypoint.sh to
extra_files so it is included in the docker build context
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore(docker): update docker-compose to use pre-built image and bind mount
- Use docker.io/sipeed/picoclaw:latest instead of building locally
- Replace named volume with bind mount ./data:/root/.picoclaw
- Move docker-compose.yml into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: update Docker Compose section to reflect new docker/ layout
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow: first run generates docker/data/config.json,
container exits, user edits config, then restarts
- Replace "Rebuild" section with "Update" (docker pull) since the
compose file now uses the pre-built sipeed/picoclaw image
- Apply same changes to README.zh.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(docker): use restart: on-failure to prevent restart after first-run setup
unless-stopped restarts the container regardless of exit code, causing
an infinite loop when entrypoint exits 0 after the initial onboard.
on-failure only restarts on non-zero exit (i.e. crashes), so the
container stays stopped after setup until the user restarts it manually.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: sync Docker Compose section across all language READMEs
Apply the same updates as the English/Chinese READMEs:
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow to first-run auto-config pattern
- Replace build/rebuild section with update via docker pull
- Affected: README.fr.md, README.ja.md, README.pt-br.md, README.vi.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-27 02:10:17 +00:00
|
|
|
|
# 3. API キーを設定
|
|
|
|
|
|
vim docker/data/config.json # プロバイダー API キー、Bot トークンなどを設定
|
|
|
|
|
|
|
|
|
|
|
|
# 4. 起動
|
|
|
|
|
|
docker compose -f docker/docker-compose.yml --profile gateway up -d
|
|
|
|
|
|
```
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-02-23 21:54:10 +00:00
|
|
|
|
> [!TIP]
|
|
|
|
|
|
> **Docker ユーザー**: デフォルトでは、Gateway は `127.0.0.1` でリッスンしており、ホストからアクセスできません。ヘルスチェックエンドポイントにアクセスしたり、ポートを公開したりする必要がある場合は、環境変数で `PICOCLAW_GATEWAY_HOST=0.0.0.0` を設定するか、`config.json` を更新してください。
|
|
|
|
|
|
|
chore(docker): reorganize docker files and add first-run entrypoint (#812)
* chore(docker): move Dockerfile into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(docker): add entrypoint script to goreleaser Dockerfile
- entrypoint.sh: on first run (config and workspace both absent) runs
picoclaw onboard then exits for the user to configure; subsequent
starts exec picoclaw gateway directly
- Dockerfile.goreleaser: copy and use entrypoint.sh, run as root
- .goreleaser.yaml: update dockerfile path, add entrypoint.sh to
extra_files so it is included in the docker build context
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore(docker): update docker-compose to use pre-built image and bind mount
- Use docker.io/sipeed/picoclaw:latest instead of building locally
- Replace named volume with bind mount ./data:/root/.picoclaw
- Move docker-compose.yml into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: update Docker Compose section to reflect new docker/ layout
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow: first run generates docker/data/config.json,
container exits, user edits config, then restarts
- Replace "Rebuild" section with "Update" (docker pull) since the
compose file now uses the pre-built sipeed/picoclaw image
- Apply same changes to README.zh.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(docker): use restart: on-failure to prevent restart after first-run setup
unless-stopped restarts the container regardless of exit code, causing
an infinite loop when entrypoint exits 0 after the initial onboard.
on-failure only restarts on non-zero exit (i.e. crashes), so the
container stays stopped after setup until the user restarts it manually.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: sync Docker Compose section across all language READMEs
Apply the same updates as the English/Chinese READMEs:
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow to first-run auto-config pattern
- Replace build/rebuild section with update via docker pull
- Affected: README.fr.md, README.ja.md, README.pt-br.md, README.vi.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-27 02:10:17 +00:00
|
|
|
|
```bash
|
|
|
|
|
|
# 5. ログ確認
|
|
|
|
|
|
docker compose -f docker/docker-compose.yml logs -f picoclaw-gateway
|
2026-02-23 21:54:10 +00:00
|
|
|
|
|
chore(docker): reorganize docker files and add first-run entrypoint (#812)
* chore(docker): move Dockerfile into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(docker): add entrypoint script to goreleaser Dockerfile
- entrypoint.sh: on first run (config and workspace both absent) runs
picoclaw onboard then exits for the user to configure; subsequent
starts exec picoclaw gateway directly
- Dockerfile.goreleaser: copy and use entrypoint.sh, run as root
- .goreleaser.yaml: update dockerfile path, add entrypoint.sh to
extra_files so it is included in the docker build context
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore(docker): update docker-compose to use pre-built image and bind mount
- Use docker.io/sipeed/picoclaw:latest instead of building locally
- Replace named volume with bind mount ./data:/root/.picoclaw
- Move docker-compose.yml into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: update Docker Compose section to reflect new docker/ layout
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow: first run generates docker/data/config.json,
container exits, user edits config, then restarts
- Replace "Rebuild" section with "Update" (docker pull) since the
compose file now uses the pre-built sipeed/picoclaw image
- Apply same changes to README.zh.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(docker): use restart: on-failure to prevent restart after first-run setup
unless-stopped restarts the container regardless of exit code, causing
an infinite loop when entrypoint exits 0 after the initial onboard.
on-failure only restarts on non-zero exit (i.e. crashes), so the
container stays stopped after setup until the user restarts it manually.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: sync Docker Compose section across all language READMEs
Apply the same updates as the English/Chinese READMEs:
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow to first-run auto-config pattern
- Replace build/rebuild section with update via docker pull
- Affected: README.fr.md, README.ja.md, README.pt-br.md, README.vi.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-27 02:10:17 +00:00
|
|
|
|
# 6. 停止
|
|
|
|
|
|
docker compose -f docker/docker-compose.yml --profile gateway down
|
2026-02-10 11:34:08 +00:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
### Agent モード(ワンショット)
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
# 質問を投げる
|
chore(docker): reorganize docker files and add first-run entrypoint (#812)
* chore(docker): move Dockerfile into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(docker): add entrypoint script to goreleaser Dockerfile
- entrypoint.sh: on first run (config and workspace both absent) runs
picoclaw onboard then exits for the user to configure; subsequent
starts exec picoclaw gateway directly
- Dockerfile.goreleaser: copy and use entrypoint.sh, run as root
- .goreleaser.yaml: update dockerfile path, add entrypoint.sh to
extra_files so it is included in the docker build context
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore(docker): update docker-compose to use pre-built image and bind mount
- Use docker.io/sipeed/picoclaw:latest instead of building locally
- Replace named volume with bind mount ./data:/root/.picoclaw
- Move docker-compose.yml into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: update Docker Compose section to reflect new docker/ layout
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow: first run generates docker/data/config.json,
container exits, user edits config, then restarts
- Replace "Rebuild" section with "Update" (docker pull) since the
compose file now uses the pre-built sipeed/picoclaw image
- Apply same changes to README.zh.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(docker): use restart: on-failure to prevent restart after first-run setup
unless-stopped restarts the container regardless of exit code, causing
an infinite loop when entrypoint exits 0 after the initial onboard.
on-failure only restarts on non-zero exit (i.e. crashes), so the
container stays stopped after setup until the user restarts it manually.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: sync Docker Compose section across all language READMEs
Apply the same updates as the English/Chinese READMEs:
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow to first-run auto-config pattern
- Replace build/rebuild section with update via docker pull
- Affected: README.fr.md, README.ja.md, README.pt-br.md, README.vi.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-27 02:10:17 +00:00
|
|
|
|
docker compose -f docker/docker-compose.yml run --rm picoclaw-agent -m "What is 2+2?"
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
# インタラクティブモード
|
chore(docker): reorganize docker files and add first-run entrypoint (#812)
* chore(docker): move Dockerfile into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(docker): add entrypoint script to goreleaser Dockerfile
- entrypoint.sh: on first run (config and workspace both absent) runs
picoclaw onboard then exits for the user to configure; subsequent
starts exec picoclaw gateway directly
- Dockerfile.goreleaser: copy and use entrypoint.sh, run as root
- .goreleaser.yaml: update dockerfile path, add entrypoint.sh to
extra_files so it is included in the docker build context
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore(docker): update docker-compose to use pre-built image and bind mount
- Use docker.io/sipeed/picoclaw:latest instead of building locally
- Replace named volume with bind mount ./data:/root/.picoclaw
- Move docker-compose.yml into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: update Docker Compose section to reflect new docker/ layout
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow: first run generates docker/data/config.json,
container exits, user edits config, then restarts
- Replace "Rebuild" section with "Update" (docker pull) since the
compose file now uses the pre-built sipeed/picoclaw image
- Apply same changes to README.zh.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(docker): use restart: on-failure to prevent restart after first-run setup
unless-stopped restarts the container regardless of exit code, causing
an infinite loop when entrypoint exits 0 after the initial onboard.
on-failure only restarts on non-zero exit (i.e. crashes), so the
container stays stopped after setup until the user restarts it manually.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: sync Docker Compose section across all language READMEs
Apply the same updates as the English/Chinese READMEs:
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow to first-run auto-config pattern
- Replace build/rebuild section with update via docker pull
- Affected: README.fr.md, README.ja.md, README.pt-br.md, README.vi.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-27 02:10:17 +00:00
|
|
|
|
docker compose -f docker/docker-compose.yml run --rm picoclaw-agent
|
2026-02-10 11:34:08 +00:00
|
|
|
|
```
|
|
|
|
|
|
|
chore(docker): reorganize docker files and add first-run entrypoint (#812)
* chore(docker): move Dockerfile into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(docker): add entrypoint script to goreleaser Dockerfile
- entrypoint.sh: on first run (config and workspace both absent) runs
picoclaw onboard then exits for the user to configure; subsequent
starts exec picoclaw gateway directly
- Dockerfile.goreleaser: copy and use entrypoint.sh, run as root
- .goreleaser.yaml: update dockerfile path, add entrypoint.sh to
extra_files so it is included in the docker build context
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore(docker): update docker-compose to use pre-built image and bind mount
- Use docker.io/sipeed/picoclaw:latest instead of building locally
- Replace named volume with bind mount ./data:/root/.picoclaw
- Move docker-compose.yml into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: update Docker Compose section to reflect new docker/ layout
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow: first run generates docker/data/config.json,
container exits, user edits config, then restarts
- Replace "Rebuild" section with "Update" (docker pull) since the
compose file now uses the pre-built sipeed/picoclaw image
- Apply same changes to README.zh.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(docker): use restart: on-failure to prevent restart after first-run setup
unless-stopped restarts the container regardless of exit code, causing
an infinite loop when entrypoint exits 0 after the initial onboard.
on-failure only restarts on non-zero exit (i.e. crashes), so the
container stays stopped after setup until the user restarts it manually.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: sync Docker Compose section across all language READMEs
Apply the same updates as the English/Chinese READMEs:
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow to first-run auto-config pattern
- Replace build/rebuild section with update via docker pull
- Affected: README.fr.md, README.ja.md, README.pt-br.md, README.vi.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-27 02:10:17 +00:00
|
|
|
|
### アップデート
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
```bash
|
chore(docker): reorganize docker files and add first-run entrypoint (#812)
* chore(docker): move Dockerfile into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(docker): add entrypoint script to goreleaser Dockerfile
- entrypoint.sh: on first run (config and workspace both absent) runs
picoclaw onboard then exits for the user to configure; subsequent
starts exec picoclaw gateway directly
- Dockerfile.goreleaser: copy and use entrypoint.sh, run as root
- .goreleaser.yaml: update dockerfile path, add entrypoint.sh to
extra_files so it is included in the docker build context
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore(docker): update docker-compose to use pre-built image and bind mount
- Use docker.io/sipeed/picoclaw:latest instead of building locally
- Replace named volume with bind mount ./data:/root/.picoclaw
- Move docker-compose.yml into docker/ directory
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: update Docker Compose section to reflect new docker/ layout
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow: first run generates docker/data/config.json,
container exits, user edits config, then restarts
- Replace "Rebuild" section with "Update" (docker pull) since the
compose file now uses the pre-built sipeed/picoclaw image
- Apply same changes to README.zh.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(docker): use restart: on-failure to prevent restart after first-run setup
unless-stopped restarts the container regardless of exit code, causing
an infinite loop when entrypoint exits 0 after the initial onboard.
on-failure only restarts on non-zero exit (i.e. crashes), so the
container stays stopped after setup until the user restarts it manually.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: sync Docker Compose section across all language READMEs
Apply the same updates as the English/Chinese READMEs:
- Use docker compose -f docker/docker-compose.yml for all commands
- Update setup flow to first-run auto-config pattern
- Replace build/rebuild section with update via docker pull
- Affected: README.fr.md, README.ja.md, README.pt-br.md, README.vi.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-27 02:10:17 +00:00
|
|
|
|
docker compose -f docker/docker-compose.yml pull
|
|
|
|
|
|
docker compose -f docker/docker-compose.yml --profile gateway up -d
|
2026-02-10 11:34:08 +00:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
### 🚀 クイックスタート(ネイティブ)
|
|
|
|
|
|
|
|
|
|
|
|
> [!TIP]
|
2026-03-13 03:15:39 +00:00
|
|
|
|
> `~/.picoclaw/config.json` に API キーを設定してください。API キーの取得先: [Volcengine (CodingPlan)](https://www.volcengine.com/activity/codingplan?utm_campaign=PicoClaw&utm_content=PicoClaw&utm_medium=devrel&utm_source=OWO&utm_term=PicoClaw) (LLM) · [OpenRouter](https://openrouter.ai/keys) (LLM) · [Zhipu](https://open.bigmodel.cn/usercenter/proj-mgmt/apikeys) (LLM)。Web 検索は **任意** です — 無料の [Tavily API](https://tavily.com) (月 1000 クエリ無料) または [Brave Search API](https://brave.com/search/api) (月 2000 クエリ無料)。
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
**1. 初期化**
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw onboard
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**2. 設定** (`~/.picoclaw/config.json`)
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
2026-02-20 15:23:22 +00:00
|
|
|
|
"model_list": [
|
|
|
|
|
|
{
|
2026-03-12 08:10:29 +00:00
|
|
|
|
"model_name": "ark-code-latest",
|
|
|
|
|
|
"model": "volcengine/ark-code-latest",
|
2026-03-14 01:30:02 +00:00
|
|
|
|
"api_key": "sk-your-api-key",
|
|
|
|
|
|
"api_base":"https://ark.cn-beijing.volces.com/api/coding/v3"
|
2026-03-12 08:10:29 +00:00
|
|
|
|
},
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_name": "gpt-5.4",
|
|
|
|
|
|
"model": "openai/gpt-5.4",
|
2026-02-20 15:23:22 +00:00
|
|
|
|
"api_key": "sk-your-openai-key",
|
2026-02-26 08:08:19 +00:00
|
|
|
|
"request_timeout": 300,
|
2026-02-20 15:23:22 +00:00
|
|
|
|
"api_base": "https://api.openai.com/v1"
|
|
|
|
|
|
}
|
|
|
|
|
|
],
|
2026-02-10 11:34:08 +00:00
|
|
|
|
"agents": {
|
|
|
|
|
|
"defaults": {
|
2026-03-12 08:10:29 +00:00
|
|
|
|
"model_name": "gpt-5.4"
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
},
|
2026-02-20 15:23:22 +00:00
|
|
|
|
"channels": {
|
|
|
|
|
|
"telegram": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"token": "YOUR_TELEGRAM_BOT_TOKEN",
|
|
|
|
|
|
"allow_from": []
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
2026-02-22 16:30:14 +00:00
|
|
|
|
},
|
|
|
|
|
|
"tools": {
|
|
|
|
|
|
"web": {
|
2026-03-15 21:12:03 +00:00
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"fetch_limit_bytes": 10485760,
|
|
|
|
|
|
"format": "plaintext",
|
2026-02-22 16:30:14 +00:00
|
|
|
|
"search": {
|
|
|
|
|
|
"api_key": "YOUR_BRAVE_API_KEY",
|
|
|
|
|
|
"max_results": 5
|
|
|
|
|
|
},
|
|
|
|
|
|
"tavily": {
|
|
|
|
|
|
"enabled": false,
|
|
|
|
|
|
"api_key": "YOUR_TAVILY_API_KEY",
|
|
|
|
|
|
"max_results": 5
|
|
|
|
|
|
}
|
|
|
|
|
|
},
|
|
|
|
|
|
"cron": {
|
|
|
|
|
|
"exec_timeout_minutes": 5
|
|
|
|
|
|
}
|
|
|
|
|
|
},
|
|
|
|
|
|
"heartbeat": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"interval": 30
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2026-02-26 08:08:19 +00:00
|
|
|
|
> **新機能**: `model_list` 形式により、プロバイダーをコード変更なしで追加できます。詳細は [モデル設定](#モデル設定-model_list) を参照してください。
|
|
|
|
|
|
> `request_timeout` は任意の秒単位設定です。省略または `<= 0` の場合、PicoClaw はデフォルトのタイムアウト(120秒)を使用します。
|
|
|
|
|
|
|
2026-02-10 11:34:08 +00:00
|
|
|
|
**3. API キーの取得**
|
|
|
|
|
|
|
2026-02-22 16:30:14 +00:00
|
|
|
|
- **LLM プロバイダー**: [OpenRouter](https://openrouter.ai/keys) · [Zhipu](https://open.bigmodel.cn/usercenter/proj-mgmt/apikeys) · [Anthropic](https://console.anthropic.com) · [OpenAI](https://platform.openai.com) · [Gemini](https://aistudio.google.com/api-keys)
|
|
|
|
|
|
- **Web 検索**(任意): [Tavily](https://tavily.com) - AI エージェント向けに最適化 (月 1000 リクエスト) · [Brave Search](https://brave.com/search/api) - 無料枠あり(月 2000 リクエスト)
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
> **注意**: 完全な設定テンプレートは `config.example.json` を参照してください。
|
|
|
|
|
|
|
2026-02-20 15:23:22 +00:00
|
|
|
|
**4. チャット**
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw agent -m "What is 2+2?"
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
これだけです!2 分で AI アシスタントが動きます。
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## 💬 チャットアプリ
|
|
|
|
|
|
|
2026-02-20 12:01:22 +00:00
|
|
|
|
Telegram、Discord、QQ、DingTalk、LINE、WeCom で PicoClaw と会話できます
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
| チャネル | セットアップ |
|
|
|
|
|
|
|---------|------------|
|
|
|
|
|
|
| **Telegram** | 簡単(トークンのみ) |
|
|
|
|
|
|
| **Discord** | 簡単(Bot トークン + Intents) |
|
2026-02-13 11:56:31 +00:00
|
|
|
|
| **QQ** | 簡単(AppID + AppSecret) |
|
|
|
|
|
|
| **DingTalk** | 普通(アプリ認証情報) |
|
2026-02-14 04:22:24 +00:00
|
|
|
|
| **LINE** | 普通(認証情報 + Webhook URL) |
|
2026-02-28 06:38:41 +00:00
|
|
|
|
| **WeCom AI Bot** | 普通(Token + AES キー) |
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
<details>
|
|
|
|
|
|
<summary><b>Telegram</b>(推奨)</summary>
|
|
|
|
|
|
|
|
|
|
|
|
**1. Bot を作成**
|
|
|
|
|
|
|
|
|
|
|
|
- Telegram を開き、`@BotFather` を検索
|
|
|
|
|
|
- `/newbot` を送信、プロンプトに従う
|
|
|
|
|
|
- トークンをコピー
|
|
|
|
|
|
|
|
|
|
|
|
**2. 設定**
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"telegram": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"token": "YOUR_BOT_TOKEN",
|
2026-02-17 16:58:10 +00:00
|
|
|
|
"allow_from": ["YOUR_USER_ID"]
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
> ユーザー ID は Telegram の `@userinfobot` から取得できます。
|
|
|
|
|
|
|
|
|
|
|
|
**3. 起動**
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw gateway
|
|
|
|
|
|
```
|
|
|
|
|
|
</details>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<details>
|
|
|
|
|
|
<summary><b>Discord</b></summary>
|
|
|
|
|
|
|
|
|
|
|
|
**1. Bot を作成**
|
|
|
|
|
|
- https://discord.com/developers/applications にアクセス
|
|
|
|
|
|
- アプリケーションを作成 → Bot → Add Bot
|
|
|
|
|
|
- Bot トークンをコピー
|
|
|
|
|
|
|
|
|
|
|
|
**2. Intents を有効化**
|
|
|
|
|
|
- Bot の設定画面で **MESSAGE CONTENT INTENT** を有効化
|
|
|
|
|
|
- (任意)**SERVER MEMBERS INTENT** も有効化
|
|
|
|
|
|
|
|
|
|
|
|
**3. ユーザー ID を取得**
|
|
|
|
|
|
- Discord 設定 → 詳細設定 → **開発者モード** を有効化
|
|
|
|
|
|
- 自分のアバターを右クリック → **ユーザーIDをコピー**
|
|
|
|
|
|
|
|
|
|
|
|
**4. 設定**
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"discord": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"token": "YOUR_BOT_TOKEN",
|
2026-02-17 16:58:10 +00:00
|
|
|
|
"allow_from": ["YOUR_USER_ID"]
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**5. Bot を招待**
|
|
|
|
|
|
- OAuth2 → URL Generator
|
|
|
|
|
|
- Scopes: `bot`
|
|
|
|
|
|
- Bot Permissions: `Send Messages`, `Read Message History`
|
|
|
|
|
|
- 生成された招待 URL を開き、サーバーに Bot を追加
|
|
|
|
|
|
|
|
|
|
|
|
**6. 起動**
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw gateway
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
</details>
|
|
|
|
|
|
|
2026-02-13 11:56:31 +00:00
|
|
|
|
<details>
|
|
|
|
|
|
<summary><b>QQ</b></summary>
|
|
|
|
|
|
|
|
|
|
|
|
**1. Bot を作成**
|
|
|
|
|
|
|
2026-02-14 04:43:44 +00:00
|
|
|
|
- [QQ オープンプラットフォーム](https://q.qq.com/#) にアクセス
|
2026-02-13 11:56:31 +00:00
|
|
|
|
- アプリケーションを作成 → **AppID** と **AppSecret** を取得
|
|
|
|
|
|
|
|
|
|
|
|
**2. 設定**
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"qq": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"app_id": "YOUR_APP_ID",
|
|
|
|
|
|
"app_secret": "YOUR_APP_SECRET",
|
|
|
|
|
|
"allow_from": []
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
> `allow_from` を空にすると全ユーザーを許可、QQ番号を指定してアクセス制限可能。
|
|
|
|
|
|
|
|
|
|
|
|
**3. 起動**
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw gateway
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
</details>
|
|
|
|
|
|
|
|
|
|
|
|
<details>
|
|
|
|
|
|
<summary><b>DingTalk</b></summary>
|
|
|
|
|
|
|
|
|
|
|
|
**1. Bot を作成**
|
|
|
|
|
|
|
|
|
|
|
|
- [オープンプラットフォーム](https://open.dingtalk.com/) にアクセス
|
|
|
|
|
|
- 内部アプリを作成
|
|
|
|
|
|
- Client ID と Client Secret をコピー
|
|
|
|
|
|
|
|
|
|
|
|
**2. 設定**
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"dingtalk": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"client_id": "YOUR_CLIENT_ID",
|
|
|
|
|
|
"client_secret": "YOUR_CLIENT_SECRET",
|
|
|
|
|
|
"allow_from": []
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
> `allow_from` を空にすると全ユーザーを許可、ユーザーIDを指定してアクセス制限可能。
|
|
|
|
|
|
|
|
|
|
|
|
**3. 起動**
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw gateway
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
</details>
|
|
|
|
|
|
|
2026-02-14 04:22:24 +00:00
|
|
|
|
<details>
|
|
|
|
|
|
<summary><b>LINE</b></summary>
|
|
|
|
|
|
|
|
|
|
|
|
**1. LINE 公式アカウントを作成**
|
|
|
|
|
|
|
|
|
|
|
|
- [LINE Developers Console](https://developers.line.biz/) にアクセス
|
|
|
|
|
|
- プロバイダーを作成 → Messaging API チャネルを作成
|
|
|
|
|
|
- **チャネルシークレット** と **チャネルアクセストークン** をコピー
|
|
|
|
|
|
|
|
|
|
|
|
**2. 設定**
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"line": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"channel_secret": "YOUR_CHANNEL_SECRET",
|
|
|
|
|
|
"channel_access_token": "YOUR_CHANNEL_ACCESS_TOKEN",
|
|
|
|
|
|
"webhook_path": "/webhook/line",
|
|
|
|
|
|
"allow_from": []
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**3. Webhook URL を設定**
|
|
|
|
|
|
|
|
|
|
|
|
LINE の Webhook には HTTPS が必要です。リバースプロキシまたはトンネルを使用してください:
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
# ngrok の例
|
2026-02-28 14:25:31 +00:00
|
|
|
|
ngrok http 18790
|
2026-02-14 04:22:24 +00:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
LINE Developers Console で Webhook URL を `https://あなたのドメイン/webhook/line` に設定し、**Webhook の利用** を有効にしてください。
|
|
|
|
|
|
|
2026-02-28 14:25:31 +00:00
|
|
|
|
> **注意**: LINE の Webhook は共有の Gateway HTTP サーバー(デフォルト: `127.0.0.1:18790`)で提供されます。ホストからアクセスする場合は Gateway のポートを公開するか、リバースプロキシを設定してください。
|
|
|
|
|
|
|
2026-02-14 04:22:24 +00:00
|
|
|
|
**4. 起動**
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw gateway
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
> グループチャットでは @メンション時のみ応答します。返信は元メッセージを引用する形式です。
|
|
|
|
|
|
|
2026-02-28 14:25:31 +00:00
|
|
|
|
> **Docker Compose**: Gateway HTTP サーバーは共有の `127.0.0.1:18790` で Webhook を提供します。ホストからアクセスするには `picoclaw-gateway` サービスに `ports: ["18790:18790"]` を追加してください。
|
2026-02-14 04:22:24 +00:00
|
|
|
|
|
|
|
|
|
|
</details>
|
|
|
|
|
|
|
2026-02-20 12:01:22 +00:00
|
|
|
|
<details>
|
|
|
|
|
|
<summary><b>WeCom (企業微信)</b></summary>
|
|
|
|
|
|
|
2026-02-28 06:38:41 +00:00
|
|
|
|
PicoClaw は3種類の WeCom 統合をサポートしています:
|
2026-02-20 12:01:22 +00:00
|
|
|
|
|
2026-02-28 06:38:41 +00:00
|
|
|
|
**オプション1: WeCom Bot (ロボット)** - 簡単な設定、グループチャット対応
|
|
|
|
|
|
**オプション2: WeCom App (カスタムアプリ)** - より多機能、アクティブメッセージング対応、プライベートチャットのみ
|
|
|
|
|
|
**オプション3: WeCom AI Bot (スマートボット)** - 公式 AI Bot、ストリーミング返信、グループ・プライベート両対応
|
2026-02-20 12:01:22 +00:00
|
|
|
|
|
2026-02-28 06:38:41 +00:00
|
|
|
|
詳細な設定手順は [WeCom AI Bot Configuration Guide](docs/channels/wecom/wecom_aibot/README.zh.md) を参照してください。
|
2026-02-20 12:01:22 +00:00
|
|
|
|
|
|
|
|
|
|
**クイックセットアップ - WeCom Bot:**
|
|
|
|
|
|
|
|
|
|
|
|
**1. ボットを作成**
|
|
|
|
|
|
|
|
|
|
|
|
* WeCom 管理コンソール → グループチャット → グループボットを追加
|
|
|
|
|
|
* Webhook URL をコピー(形式: `https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=xxx`)
|
|
|
|
|
|
|
|
|
|
|
|
**2. 設定**
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"wecom": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"token": "YOUR_TOKEN",
|
|
|
|
|
|
"encoding_aes_key": "YOUR_ENCODING_AES_KEY",
|
|
|
|
|
|
"webhook_url": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=YOUR_KEY",
|
|
|
|
|
|
"webhook_path": "/webhook/wecom",
|
|
|
|
|
|
"allow_from": []
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
2026-02-28 14:25:31 +00:00
|
|
|
|
|
|
|
|
|
|
> **注意**: WeCom Bot の Webhook 受信は共有の Gateway HTTP サーバー(デフォルト: `127.0.0.1:18790`)で提供されます。ホストからアクセスする場合は Gateway のポートを公開するか、HTTPS 用のリバースプロキシを設定してください。
|
2026-02-20 12:01:22 +00:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**クイックセットアップ - WeCom App:**
|
|
|
|
|
|
|
|
|
|
|
|
**1. アプリを作成**
|
|
|
|
|
|
|
|
|
|
|
|
* WeCom 管理コンソール → アプリ管理 → アプリを作成
|
|
|
|
|
|
* **AgentId** と **Secret** をコピー
|
|
|
|
|
|
* "マイ会社" ページで **CorpID** をコピー
|
|
|
|
|
|
|
|
|
|
|
|
**2. メッセージ受信を設定**
|
|
|
|
|
|
|
|
|
|
|
|
* アプリ詳細で "メッセージを受信" → "APIを設定" をクリック
|
2026-02-28 14:25:31 +00:00
|
|
|
|
* URL を `http://your-server:18790/webhook/wecom-app` に設定
|
2026-02-20 12:01:22 +00:00
|
|
|
|
* **Token** と **EncodingAESKey** を生成
|
|
|
|
|
|
|
|
|
|
|
|
**3. 設定**
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"wecom_app": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"corp_id": "wwxxxxxxxxxxxxxxxx",
|
|
|
|
|
|
"corp_secret": "YOUR_CORP_SECRET",
|
|
|
|
|
|
"agent_id": 1000002,
|
|
|
|
|
|
"token": "YOUR_TOKEN",
|
|
|
|
|
|
"encoding_aes_key": "YOUR_ENCODING_AES_KEY",
|
|
|
|
|
|
"webhook_path": "/webhook/wecom-app",
|
|
|
|
|
|
"allow_from": []
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**4. 起動**
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw gateway
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2026-02-28 14:25:31 +00:00
|
|
|
|
> **注意**: WeCom App の Webhook コールバックは共有の Gateway HTTP サーバー(デフォルト: `127.0.0.1:18790`)で提供されます。ホストからアクセスする場合は HTTPS 用のリバースプロキシを設定してください。
|
2026-02-20 12:01:22 +00:00
|
|
|
|
|
2026-02-28 06:38:41 +00:00
|
|
|
|
**クイックセットアップ - WeCom AI Bot:**
|
|
|
|
|
|
|
|
|
|
|
|
**1. AI Bot を作成**
|
|
|
|
|
|
|
|
|
|
|
|
* WeCom 管理コンソール → アプリ管理 → AI Bot
|
|
|
|
|
|
* コールバック URL を設定: `http://your-server:18791/webhook/wecom-aibot`
|
|
|
|
|
|
* **Token** をコピーし、**EncodingAESKey** を生成
|
|
|
|
|
|
|
|
|
|
|
|
**2. 設定**
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"wecom_aibot": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"token": "YOUR_TOKEN",
|
|
|
|
|
|
"encoding_aes_key": "YOUR_43_CHAR_ENCODING_AES_KEY",
|
|
|
|
|
|
"webhook_path": "/webhook/wecom-aibot",
|
|
|
|
|
|
"allow_from": [],
|
|
|
|
|
|
"welcome_message": "こんにちは!何かお手伝いできますか?"
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**3. 起動**
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw gateway
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2026-02-28 07:50:32 +00:00
|
|
|
|
> **注意**: WeCom AI Bot はストリーミングプルプロトコルを使用 — 返信タイムアウトの心配なし。長時間タスク(>30秒)は自動的に `response_url` によるプッシュ配信に切り替わります。
|
2026-02-28 06:38:41 +00:00
|
|
|
|
|
2026-02-20 12:01:22 +00:00
|
|
|
|
</details>
|
|
|
|
|
|
|
2026-02-13 07:19:37 +00:00
|
|
|
|
## ⚙️ 設定
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-02-13 07:19:37 +00:00
|
|
|
|
設定ファイル: `~/.picoclaw/config.json`
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-03-01 20:41:12 +00:00
|
|
|
|
### 環境変数
|
|
|
|
|
|
|
|
|
|
|
|
環境変数を使用してデフォルトのパスを上書きできます。これは、ポータブルインストール、コンテナ化されたデプロイメント、または picoclaw をシステムサービスとして実行する場合に便利です。これらの変数は独立しており、異なるパスを制御します。
|
|
|
|
|
|
|
|
|
|
|
|
| 変数 | 説明 | デフォルトパス |
|
|
|
|
|
|
|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
|
|
|
|
|
|
| `PICOCLAW_CONFIG` | 設定ファイルへのパスを上書きします。これにより、picoclaw は他のすべての場所を無視して、指定された `config.json` をロードします。 | `~/.picoclaw/config.json` |
|
|
|
|
|
|
| `PICOCLAW_HOME` | picoclaw データのルートディレクトリを上書きします。これにより、`workspace` やその他のデータディレクトリのデフォルトの場所が変更されます。 | `~/.picoclaw` |
|
|
|
|
|
|
|
|
|
|
|
|
**例:**
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
# 特定の設定ファイルを使用して picoclaw を実行する
|
|
|
|
|
|
# ワークスペースのパスはその設定ファイル内から読み込まれます
|
|
|
|
|
|
PICOCLAW_CONFIG=/etc/picoclaw/production.json picoclaw gateway
|
|
|
|
|
|
|
|
|
|
|
|
# すべてのデータを /opt/picoclaw に保存して picoclaw を実行する
|
|
|
|
|
|
# 設定はデフォルトの ~/.picoclaw/config.json からロードされます
|
|
|
|
|
|
# ワークスペースは /opt/picoclaw/workspace に作成されます
|
|
|
|
|
|
PICOCLAW_HOME=/opt/picoclaw picoclaw agent
|
|
|
|
|
|
|
|
|
|
|
|
# 両方を使用して完全にカスタマイズされたセットアップを行う
|
|
|
|
|
|
PICOCLAW_HOME=/srv/picoclaw PICOCLAW_CONFIG=/srv/picoclaw/main.json picoclaw gateway
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2026-02-13 07:19:37 +00:00
|
|
|
|
### ワークスペース構成
|
|
|
|
|
|
|
|
|
|
|
|
PicoClaw は設定されたワークスペース(デフォルト: `~/.picoclaw/workspace`)にデータを保存します:
|
|
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
~/.picoclaw/workspace/
|
|
|
|
|
|
├── sessions/ # 会話セッションと履歴
|
|
|
|
|
|
├── memory/ # 長期メモリ(MEMORY.md)
|
|
|
|
|
|
├── state/ # 永続状態(最後のチャネルなど)
|
|
|
|
|
|
├── cron/ # スケジュールジョブデータベース
|
|
|
|
|
|
├── skills/ # カスタムスキル
|
|
|
|
|
|
├── AGENTS.md # エージェントの行動ガイド
|
|
|
|
|
|
├── HEARTBEAT.md # 定期タスクプロンプト(30分ごとに確認)
|
|
|
|
|
|
├── IDENTITY.md # エージェントのアイデンティティ
|
|
|
|
|
|
├── SOUL.md # エージェントのソウル
|
|
|
|
|
|
└── USER.md # ユーザー設定
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2026-02-13 11:33:21 +00:00
|
|
|
|
### 🔒 セキュリティサンドボックス
|
|
|
|
|
|
|
|
|
|
|
|
PicoClaw はデフォルトでサンドボックス環境で実行されます。エージェントは設定されたワークスペース内のファイルにのみアクセスし、コマンドを実行できます。
|
|
|
|
|
|
|
|
|
|
|
|
#### デフォルト設定
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"agents": {
|
|
|
|
|
|
"defaults": {
|
|
|
|
|
|
"workspace": "~/.picoclaw/workspace",
|
|
|
|
|
|
"restrict_to_workspace": true
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
| オプション | デフォルト | 説明 |
|
|
|
|
|
|
|-----------|-----------|------|
|
|
|
|
|
|
| `workspace` | `~/.picoclaw/workspace` | エージェントの作業ディレクトリ |
|
|
|
|
|
|
| `restrict_to_workspace` | `true` | ファイル/コマンドアクセスをワークスペースに制限 |
|
|
|
|
|
|
|
|
|
|
|
|
#### 保護対象ツール
|
|
|
|
|
|
|
|
|
|
|
|
`restrict_to_workspace: true` の場合、以下のツールがサンドボックス化されます:
|
|
|
|
|
|
|
|
|
|
|
|
| ツール | 機能 | 制限 |
|
|
|
|
|
|
|-------|------|------|
|
|
|
|
|
|
| `read_file` | ファイル読み込み | ワークスペース内のファイルのみ |
|
|
|
|
|
|
| `write_file` | ファイル書き込み | ワークスペース内のファイルのみ |
|
|
|
|
|
|
| `list_dir` | ディレクトリ一覧 | ワークスペース内のディレクトリのみ |
|
|
|
|
|
|
| `edit_file` | ファイル編集 | ワークスペース内のファイルのみ |
|
|
|
|
|
|
| `append_file` | ファイル追記 | ワークスペース内のファイルのみ |
|
|
|
|
|
|
| `exec` | コマンド実行 | コマンドパスはワークスペース内である必要あり |
|
|
|
|
|
|
|
|
|
|
|
|
#### exec ツールの追加保護
|
|
|
|
|
|
|
|
|
|
|
|
`restrict_to_workspace: false` でも、`exec` ツールは以下の危険なコマンドをブロックします:
|
|
|
|
|
|
|
|
|
|
|
|
- `rm -rf`, `del /f`, `rmdir /s` — 一括削除
|
|
|
|
|
|
- `format`, `mkfs`, `diskpart` — ディスクフォーマット
|
|
|
|
|
|
- `dd if=` — ディスクイメージング
|
|
|
|
|
|
- `/dev/sd[a-z]` への書き込み — 直接ディスク書き込み
|
|
|
|
|
|
- `shutdown`, `reboot`, `poweroff` — システムシャットダウン
|
|
|
|
|
|
- フォークボム `:(){ :|:& };:`
|
|
|
|
|
|
|
|
|
|
|
|
#### エラー例
|
|
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
[ERROR] tool: Tool execution failed
|
|
|
|
|
|
{tool=exec, error=Command blocked by safety guard (path outside working dir)}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
[ERROR] tool: Tool execution failed
|
|
|
|
|
|
{tool=exec, error=Command blocked by safety guard (dangerous pattern detected)}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
#### 制限の無効化(セキュリティリスク)
|
|
|
|
|
|
|
|
|
|
|
|
エージェントにワークスペース外のパスへのアクセスが必要な場合:
|
|
|
|
|
|
|
|
|
|
|
|
**方法1: 設定ファイル**
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"agents": {
|
|
|
|
|
|
"defaults": {
|
|
|
|
|
|
"restrict_to_workspace": false
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**方法2: 環境変数**
|
|
|
|
|
|
```bash
|
|
|
|
|
|
export PICOCLAW_AGENTS_DEFAULTS_RESTRICT_TO_WORKSPACE=false
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
> ⚠️ **警告**: この制限を無効にすると、エージェントはシステム上の任意のパスにアクセスできるようになります。制御された環境でのみ慎重に使用してください。
|
|
|
|
|
|
|
|
|
|
|
|
#### セキュリティ境界の一貫性
|
|
|
|
|
|
|
|
|
|
|
|
`restrict_to_workspace` 設定は、すべての実行パスで一貫して適用されます:
|
|
|
|
|
|
|
|
|
|
|
|
| 実行パス | セキュリティ境界 |
|
|
|
|
|
|
|---------|-----------------|
|
|
|
|
|
|
| メインエージェント | `restrict_to_workspace` ✅ |
|
|
|
|
|
|
| サブエージェント / Spawn | 同じ制限を継承 ✅ |
|
|
|
|
|
|
| ハートビートタスク | 同じ制限を継承 ✅ |
|
|
|
|
|
|
|
|
|
|
|
|
すべてのパスで同じワークスペース制限が適用されます — サブエージェントやスケジュールタスクを通じてセキュリティ境界をバイパスする方法はありません。
|
|
|
|
|
|
|
2026-02-13 07:19:37 +00:00
|
|
|
|
### ハートビート(定期タスク)
|
|
|
|
|
|
|
|
|
|
|
|
PicoClaw は自動的に定期タスクを実行できます。ワークスペースに `HEARTBEAT.md` ファイルを作成します:
|
|
|
|
|
|
|
|
|
|
|
|
```markdown
|
|
|
|
|
|
# 定期タスク
|
|
|
|
|
|
|
|
|
|
|
|
- 重要なメールをチェック
|
|
|
|
|
|
- 今後の予定を確認
|
|
|
|
|
|
- 天気予報をチェック
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
エージェントは30分ごと(設定可能)にこのファイルを読み込み、利用可能なツールを使ってタスクを実行します。
|
|
|
|
|
|
|
|
|
|
|
|
#### spawn で非同期タスク実行
|
|
|
|
|
|
|
|
|
|
|
|
時間のかかるタスク(Web検索、API呼び出し)には `spawn` ツールを使って**サブエージェント**を作成します:
|
|
|
|
|
|
|
|
|
|
|
|
```markdown
|
|
|
|
|
|
# 定期タスク
|
|
|
|
|
|
|
|
|
|
|
|
## クイックタスク(直接応答)
|
|
|
|
|
|
- 現在時刻を報告
|
|
|
|
|
|
|
|
|
|
|
|
## 長時間タスク(spawn で非同期)
|
|
|
|
|
|
- AIニュースを検索して要約
|
|
|
|
|
|
- メールをチェックして重要なメッセージを報告
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**主な特徴:**
|
|
|
|
|
|
|
|
|
|
|
|
| 機能 | 説明 |
|
|
|
|
|
|
|------|------|
|
|
|
|
|
|
| **spawn** | 非同期サブエージェントを作成、ハートビートをブロックしない |
|
|
|
|
|
|
| **独立コンテキスト** | サブエージェントは独自のコンテキストを持ち、セッション履歴なし |
|
|
|
|
|
|
| **message ツール** | サブエージェントは message ツールで直接ユーザーと通信 |
|
|
|
|
|
|
| **非ブロッキング** | spawn 後、ハートビートは次のタスクへ継続 |
|
|
|
|
|
|
|
|
|
|
|
|
#### サブエージェントの通信方法
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-02-13 07:19:37 +00:00
|
|
|
|
```
|
|
|
|
|
|
ハートビート発動
|
|
|
|
|
|
↓
|
|
|
|
|
|
エージェントが HEARTBEAT.md を読む
|
|
|
|
|
|
↓
|
|
|
|
|
|
長いタスク: spawn サブエージェント
|
|
|
|
|
|
↓ ↓
|
|
|
|
|
|
次のタスクへ継続 サブエージェントが独立して動作
|
|
|
|
|
|
↓ ↓
|
|
|
|
|
|
全タスク完了 message ツールを使用
|
|
|
|
|
|
↓ ↓
|
|
|
|
|
|
HEARTBEAT_OK 応答 ユーザーが直接結果を受け取る
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
サブエージェントはツール(message、web_search など)にアクセスでき、メインエージェントを経由せずにユーザーと通信できます。
|
|
|
|
|
|
|
|
|
|
|
|
**設定:**
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"heartbeat": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"interval": 30
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
| オプション | デフォルト | 説明 |
|
|
|
|
|
|
|-----------|-----------|------|
|
|
|
|
|
|
| `enabled` | `true` | ハートビートの有効/無効 |
|
|
|
|
|
|
| `interval` | `30` | チェック間隔(分)、最小5分 |
|
|
|
|
|
|
|
|
|
|
|
|
**環境変数:**
|
|
|
|
|
|
- `PICOCLAW_HEARTBEAT_ENABLED=false` で無効化
|
|
|
|
|
|
- `PICOCLAW_HEARTBEAT_INTERVAL=60` で間隔変更
|
|
|
|
|
|
|
2026-02-16 23:23:44 +00:00
|
|
|
|
### プロバイダー
|
|
|
|
|
|
|
|
|
|
|
|
> [!NOTE]
|
2026-03-01 08:31:04 +00:00
|
|
|
|
> Groq は Whisper による無料の音声文字起こしを提供しています。設定すると、あらゆるチャンネルからの音声メッセージがエージェントレベルで自動的に文字起こしされます。
|
2026-02-16 23:23:44 +00:00
|
|
|
|
|
|
|
|
|
|
| プロバイダー | 用途 | API キー取得先 |
|
|
|
|
|
|
| --- | --- | --- |
|
|
|
|
|
|
| `gemini` | LLM(Gemini 直接) | [aistudio.google.com](https://aistudio.google.com) |
|
|
|
|
|
|
| `zhipu` | LLM(Zhipu 直接) | [bigmodel.cn](https://bigmodel.cn) |
|
2026-03-13 03:15:39 +00:00
|
|
|
|
| `volcengine` | LLM(Volcengine 直接) | [volcengine.com](https://www.volcengine.com/activity/codingplan?utm_campaign=PicoClaw&utm_content=PicoClaw&utm_medium=devrel&utm_source=OWO&utm_term=PicoClaw) |
|
2026-02-16 23:25:21 +00:00
|
|
|
|
| `openrouter`(要テスト) | LLM(推奨、全モデルにアクセス可能) | [openrouter.ai](https://openrouter.ai) |
|
|
|
|
|
|
| `anthropic`(要テスト) | LLM(Claude 直接) | [console.anthropic.com](https://console.anthropic.com) |
|
|
|
|
|
|
| `openai`(要テスト) | LLM(GPT 直接) | [platform.openai.com](https://platform.openai.com) |
|
|
|
|
|
|
| `deepseek`(要テスト) | LLM(DeepSeek 直接) | [platform.deepseek.com](https://platform.deepseek.com) |
|
2026-02-16 23:23:44 +00:00
|
|
|
|
| `groq` | LLM + **音声文字起こし**(Whisper) | [console.groq.com](https://console.groq.com) |
|
|
|
|
|
|
| `cerebras` | LLM(Cerebras 直接) | [cerebras.ai](https://cerebras.ai) |
|
|
|
|
|
|
|
2026-02-13 07:19:37 +00:00
|
|
|
|
### 基本設定
|
|
|
|
|
|
|
|
|
|
|
|
1. **設定ファイルの作成:**
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-02-11 15:44:10 +00:00
|
|
|
|
```bash
|
|
|
|
|
|
cp config.example.json config/config.json
|
|
|
|
|
|
```
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-02-11 15:44:10 +00:00
|
|
|
|
2. **設定の編集:**
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-02-11 15:44:10 +00:00
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"providers": {
|
|
|
|
|
|
"openrouter": {
|
|
|
|
|
|
"api_key": "sk-or-v1-..."
|
|
|
|
|
|
}
|
|
|
|
|
|
},
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"discord": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"token": "YOUR_DISCORD_BOT_TOKEN"
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
2026-02-11 15:44:10 +00:00
|
|
|
|
```
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-02-13 07:19:37 +00:00
|
|
|
|
3. **実行**
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
2026-02-13 07:19:37 +00:00
|
|
|
|
```bash
|
|
|
|
|
|
picoclaw agent -m "Hello"
|
|
|
|
|
|
```
|
2026-02-10 11:34:08 +00:00
|
|
|
|
</details>
|
|
|
|
|
|
|
|
|
|
|
|
<details>
|
|
|
|
|
|
<summary><b>完全な設定例</b></summary>
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"agents": {
|
|
|
|
|
|
"defaults": {
|
|
|
|
|
|
"model": "anthropic/claude-opus-4-5"
|
|
|
|
|
|
}
|
|
|
|
|
|
},
|
|
|
|
|
|
"providers": {
|
|
|
|
|
|
"openrouter": {
|
2026-02-20 15:23:22 +00:00
|
|
|
|
"api_key": "sk-or-v1-xxx"
|
2026-02-10 11:34:08 +00:00
|
|
|
|
},
|
|
|
|
|
|
"groq": {
|
2026-02-20 15:23:22 +00:00
|
|
|
|
"api_key": "gsk_xxx"
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
},
|
|
|
|
|
|
"channels": {
|
|
|
|
|
|
"telegram": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"token": "123456:ABC...",
|
2026-02-17 16:58:10 +00:00
|
|
|
|
"allow_from": ["123456789"]
|
2026-02-10 11:34:08 +00:00
|
|
|
|
},
|
|
|
|
|
|
"discord": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"token": "",
|
|
|
|
|
|
"allow_from": [""]
|
|
|
|
|
|
},
|
|
|
|
|
|
"whatsapp": {
|
|
|
|
|
|
"enabled": false
|
|
|
|
|
|
},
|
|
|
|
|
|
"feishu": {
|
|
|
|
|
|
"enabled": false,
|
2026-02-20 15:23:22 +00:00
|
|
|
|
"app_id": "cli_xxx",
|
|
|
|
|
|
"app_secret": "xxx",
|
|
|
|
|
|
"encrypt_key": "",
|
|
|
|
|
|
"verification_token": "",
|
2026-02-17 16:58:10 +00:00
|
|
|
|
"allow_from": []
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
},
|
|
|
|
|
|
"tools": {
|
|
|
|
|
|
"web": {
|
|
|
|
|
|
"search": {
|
2026-02-20 15:23:22 +00:00
|
|
|
|
"api_key": "BSA..."
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
2026-02-15 10:41:39 +00:00
|
|
|
|
},
|
|
|
|
|
|
"cron": {
|
|
|
|
|
|
"exec_timeout_minutes": 5
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
2026-02-13 07:19:37 +00:00
|
|
|
|
},
|
|
|
|
|
|
"heartbeat": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"interval": 30
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
</details>
|
|
|
|
|
|
|
2026-02-19 17:22:06 +00:00
|
|
|
|
### モデル設定 (model_list)
|
|
|
|
|
|
|
|
|
|
|
|
> **新機能!** PicoClaw は現在 **モデル中心** の設定アプローチを採用しています。`ベンダー/モデル` 形式(例: `zhipu/glm-4.7`)を指定するだけで、新しいプロバイダーを追加できます—**コードの変更は一切不要!**
|
|
|
|
|
|
|
|
|
|
|
|
この設計は、柔軟なプロバイダー選択による **マルチエージェントサポート** も可能にします:
|
|
|
|
|
|
|
|
|
|
|
|
- **異なるエージェント、異なるプロバイダー** : 各エージェントは独自の LLM プロバイダーを使用可能
|
|
|
|
|
|
- **フォールバックモデル** : 耐障性のため、プライマリモデルとフォールバックモデルを設定可能
|
|
|
|
|
|
- **ロードバランシング** : 複数のエンドポイントにリクエストを分散
|
|
|
|
|
|
- **集中設定管理** : すべてのプロバイダーを一箇所で管理
|
|
|
|
|
|
|
|
|
|
|
|
#### 📋 サポートされているすべてのベンダー
|
|
|
|
|
|
|
|
|
|
|
|
| ベンダー | `model` プレフィックス | デフォルト API Base | プロトコル | API キー |
|
|
|
|
|
|
|-------------|-----------------|---------------------|----------|---------|
|
|
|
|
|
|
| **OpenAI** | `openai/` | `https://api.openai.com/v1` | OpenAI | [キーを取得](https://platform.openai.com) |
|
|
|
|
|
|
| **Anthropic** | `anthropic/` | `https://api.anthropic.com/v1` | Anthropic | [キーを取得](https://console.anthropic.com) |
|
|
|
|
|
|
| **Zhipu AI (GLM)** | `zhipu/` | `https://open.bigmodel.cn/api/paas/v4` | OpenAI | [キーを取得](https://open.bigmodel.cn/usercenter/proj-mgmt/apikeys) |
|
|
|
|
|
|
| **DeepSeek** | `deepseek/` | `https://api.deepseek.com/v1` | OpenAI | [キーを取得](https://platform.deepseek.com) |
|
|
|
|
|
|
| **Google Gemini** | `gemini/` | `https://generativelanguage.googleapis.com/v1beta` | OpenAI | [キーを取得](https://aistudio.google.com/api-keys) |
|
|
|
|
|
|
| **Groq** | `groq/` | `https://api.groq.com/openai/v1` | OpenAI | [キーを取得](https://console.groq.com) |
|
|
|
|
|
|
| **Moonshot** | `moonshot/` | `https://api.moonshot.cn/v1` | OpenAI | [キーを取得](https://platform.moonshot.cn) |
|
|
|
|
|
|
| **Qwen (Alibaba)** | `qwen/` | `https://dashscope.aliyuncs.com/compatible-mode/v1` | OpenAI | [キーを取得](https://dashscope.console.aliyun.com) |
|
|
|
|
|
|
| **NVIDIA** | `nvidia/` | `https://integrate.api.nvidia.com/v1` | OpenAI | [キーを取得](https://build.nvidia.com) |
|
|
|
|
|
|
| **Ollama** | `ollama/` | `http://localhost:11434/v1` | OpenAI | ローカル(キー不要) |
|
|
|
|
|
|
| **OpenRouter** | `openrouter/` | `https://openrouter.ai/api/v1` | OpenAI | [キーを取得](https://openrouter.ai/keys) |
|
|
|
|
|
|
| **VLLM** | `vllm/` | `http://localhost:8000/v1` | OpenAI | ローカル |
|
|
|
|
|
|
| **Cerebras** | `cerebras/` | `https://api.cerebras.ai/v1` | OpenAI | [キーを取得](https://cerebras.ai) |
|
2026-03-13 03:15:39 +00:00
|
|
|
|
| **VolcEngine (Doubao)** | `volcengine/` | `https://ark.cn-beijing.volces.com/api/v3` | OpenAI | [キーを取得](https://www.volcengine.com/activity/codingplan?utm_campaign=PicoClaw&utm_content=PicoClaw&utm_medium=devrel&utm_source=OWO&utm_term=PicoClaw) |
|
2026-02-19 17:22:06 +00:00
|
|
|
|
| **ShengsuanYun** | `shengsuanyun/` | `https://router.shengsuanyun.com/api/v1` | OpenAI | - |
|
2026-03-13 03:15:39 +00:00
|
|
|
|
| **BytePlus** | `byteplus/` | `https://ark.ap-southeast.bytepluses.com/api/v3` | OpenAI | [キーを取得](https://www.byteplus.com) |
|
2026-03-11 18:34:42 +00:00
|
|
|
|
| **LongCat** | `longcat/` | `https://api.longcat.chat/openai` | OpenAI | [キーを取得](https://longcat.chat/platform) |
|
2026-03-13 06:02:23 +00:00
|
|
|
|
| **ModelScope (魔搭)**| `modelscope/` | `https://api-inference.modelscope.cn/v1` | OpenAI | [トークンを取得](https://modelscope.cn/my/tokens) |
|
2026-03-14 14:52:34 +00:00
|
|
|
|
| **Azure OpenAI** | `azure/` | `https://{resource}.openai.azure.com` | Azure | [キーを取得](https://portal.azure.com) |
|
2026-02-19 17:22:06 +00:00
|
|
|
|
| **Antigravity** | `antigravity/` | Google Cloud | カスタム | OAuthのみ |
|
|
|
|
|
|
| **GitHub Copilot** | `github-copilot/` | `localhost:4321` | gRPC | - |
|
|
|
|
|
|
|
|
|
|
|
|
#### 基本設定
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_list": [
|
|
|
|
|
|
{
|
2026-03-12 08:10:29 +00:00
|
|
|
|
"model_name": "ark-code-latest",
|
|
|
|
|
|
"model": "volcengine/ark-code-latest",
|
|
|
|
|
|
"api_key": "sk-your-api-key"
|
|
|
|
|
|
},
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_name": "gpt-5.4",
|
|
|
|
|
|
"model": "openai/gpt-5.4",
|
2026-02-19 17:22:06 +00:00
|
|
|
|
"api_key": "sk-your-openai-key"
|
|
|
|
|
|
},
|
|
|
|
|
|
{
|
2026-02-20 04:15:04 +00:00
|
|
|
|
"model_name": "claude-sonnet-4.6",
|
|
|
|
|
|
"model": "anthropic/claude-sonnet-4.6",
|
2026-02-19 17:22:06 +00:00
|
|
|
|
"api_key": "sk-ant-your-key"
|
|
|
|
|
|
},
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_name": "glm-4.7",
|
|
|
|
|
|
"model": "zhipu/glm-4.7",
|
|
|
|
|
|
"api_key": "your-zhipu-key"
|
|
|
|
|
|
}
|
|
|
|
|
|
],
|
|
|
|
|
|
"agents": {
|
|
|
|
|
|
"defaults": {
|
2026-03-12 08:10:29 +00:00
|
|
|
|
"model": "gpt-5.4"
|
2026-02-19 17:22:06 +00:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
#### ベンダー別の例
|
|
|
|
|
|
|
|
|
|
|
|
**OpenAI**
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
2026-03-12 08:10:29 +00:00
|
|
|
|
"model_name": "gpt-5.4",
|
|
|
|
|
|
"model": "openai/gpt-5.4",
|
|
|
|
|
|
"api_key": "sk-..."
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**VolcEngine (Doubao)**
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_name": "ark-code-latest",
|
|
|
|
|
|
"model": "volcengine/ark-code-latest",
|
2026-02-19 17:22:06 +00:00
|
|
|
|
"api_key": "sk-..."
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**Zhipu AI (GLM)**
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_name": "glm-4.7",
|
|
|
|
|
|
"model": "zhipu/glm-4.7",
|
|
|
|
|
|
"api_key": "your-key"
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**Anthropic (OAuth使用)**
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
2026-02-20 04:15:04 +00:00
|
|
|
|
"model_name": "claude-sonnet-4.6",
|
|
|
|
|
|
"model": "anthropic/claude-sonnet-4.6",
|
2026-02-19 17:22:06 +00:00
|
|
|
|
"auth_method": "oauth"
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
> OAuth認証を設定するには、`picoclaw auth login --provider anthropic` を実行してください。
|
|
|
|
|
|
|
2026-02-26 08:08:19 +00:00
|
|
|
|
**カスタムプロキシ/API**
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_name": "my-custom-model",
|
|
|
|
|
|
"model": "openai/custom-model",
|
|
|
|
|
|
"api_base": "https://my-proxy.com/v1",
|
|
|
|
|
|
"api_key": "sk-...",
|
|
|
|
|
|
"request_timeout": 300
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2026-02-19 17:22:06 +00:00
|
|
|
|
#### ロードバランシング
|
|
|
|
|
|
|
|
|
|
|
|
同じモデル名で複数のエンドポイントを設定すると、PicoClaw が自動的にラウンドロビンで分散します:
|
|
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_list": [
|
|
|
|
|
|
{
|
2026-03-12 08:10:29 +00:00
|
|
|
|
"model_name": "gpt-5.4",
|
|
|
|
|
|
"model": "openai/gpt-5.4",
|
2026-02-19 17:22:06 +00:00
|
|
|
|
"api_base": "https://api1.example.com/v1",
|
|
|
|
|
|
"api_key": "sk-key1"
|
|
|
|
|
|
},
|
|
|
|
|
|
{
|
2026-03-12 08:10:29 +00:00
|
|
|
|
"model_name": "gpt-5.4",
|
|
|
|
|
|
"model": "openai/gpt-5.4",
|
2026-02-19 17:22:06 +00:00
|
|
|
|
"api_base": "https://api2.example.com/v1",
|
|
|
|
|
|
"api_key": "sk-key2"
|
|
|
|
|
|
}
|
|
|
|
|
|
]
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
#### 従来の `providers` 設定からの移行
|
|
|
|
|
|
|
|
|
|
|
|
古い `providers` 設定は**非推奨**ですが、後方互換性のためにサポートされています。
|
|
|
|
|
|
|
|
|
|
|
|
**旧設定(非推奨):**
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"providers": {
|
|
|
|
|
|
"zhipu": {
|
|
|
|
|
|
"api_key": "your-key",
|
|
|
|
|
|
"api_base": "https://open.bigmodel.cn/api/paas/v4"
|
|
|
|
|
|
}
|
|
|
|
|
|
},
|
|
|
|
|
|
"agents": {
|
|
|
|
|
|
"defaults": {
|
|
|
|
|
|
"provider": "zhipu",
|
|
|
|
|
|
"model": "glm-4.7"
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
**新設定(推奨):**
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_list": [
|
|
|
|
|
|
{
|
|
|
|
|
|
"model_name": "glm-4.7",
|
|
|
|
|
|
"model": "zhipu/glm-4.7",
|
|
|
|
|
|
"api_key": "your-key"
|
|
|
|
|
|
}
|
|
|
|
|
|
],
|
|
|
|
|
|
"agents": {
|
|
|
|
|
|
"defaults": {
|
|
|
|
|
|
"model": "glm-4.7"
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
詳細な移行ガイドは、[docs/migration/model-list-migration.md](docs/migration/model-list-migration.md) を参照してください。
|
|
|
|
|
|
|
2026-02-10 11:34:08 +00:00
|
|
|
|
## CLI リファレンス
|
|
|
|
|
|
|
|
|
|
|
|
| コマンド | 説明 |
|
|
|
|
|
|
|---------|------|
|
|
|
|
|
|
| `picoclaw onboard` | 設定&ワークスペースの初期化 |
|
|
|
|
|
|
| `picoclaw agent -m "..."` | エージェントとチャット |
|
|
|
|
|
|
| `picoclaw agent` | インタラクティブチャットモード |
|
|
|
|
|
|
| `picoclaw gateway` | ゲートウェイを起動 |
|
|
|
|
|
|
| `picoclaw status` | ステータスを表示 |
|
|
|
|
|
|
|
|
|
|
|
|
## 🤝 コントリビュート&ロードマップ
|
|
|
|
|
|
|
|
|
|
|
|
PR 歓迎!コードベースは意図的に小さく読みやすくしています。🤗
|
|
|
|
|
|
|
|
|
|
|
|
Discord: https://discord.gg/V4sAZ9XWpN
|
|
|
|
|
|
|
|
|
|
|
|
<img src="assets/wechat.png" alt="PicoClaw" width="512">
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## 🐛 トラブルシューティング
|
|
|
|
|
|
|
2026-02-15 14:56:13 +00:00
|
|
|
|
### Web 検索で「API 設定の問題」と表示される
|
2026-02-10 11:34:08 +00:00
|
|
|
|
|
|
|
|
|
|
検索 API キーをまだ設定していない場合、これは正常です。PicoClaw は手動検索用の便利なリンクを提供します。
|
|
|
|
|
|
|
|
|
|
|
|
Web 検索を有効にするには:
|
2026-02-22 16:30:14 +00:00
|
|
|
|
1. [https://tavily.com](https://tavily.com) (月 1000 クエリ無料) または [https://brave.com/search/api](https://brave.com/search/api) で無料の API キーを取得(月 2000 クエリ無料)
|
2026-02-10 11:34:08 +00:00
|
|
|
|
2. `~/.picoclaw/config.json` に追加:
|
|
|
|
|
|
```json
|
|
|
|
|
|
{
|
|
|
|
|
|
"tools": {
|
|
|
|
|
|
"web": {
|
2026-02-20 15:23:22 +00:00
|
|
|
|
"brave": {
|
|
|
|
|
|
"enabled": true,
|
2026-02-10 11:34:08 +00:00
|
|
|
|
"api_key": "YOUR_BRAVE_API_KEY",
|
|
|
|
|
|
"max_results": 5
|
2026-02-20 15:23:22 +00:00
|
|
|
|
},
|
|
|
|
|
|
"duckduckgo": {
|
|
|
|
|
|
"enabled": true,
|
|
|
|
|
|
"max_results": 5
|
2026-02-10 11:34:08 +00:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
### コンテンツフィルタリングエラーが出る
|
|
|
|
|
|
|
|
|
|
|
|
一部のプロバイダー(Zhipu など)にはコンテンツフィルタリングがあります。クエリを言い換えるか、別のモデルを使用してください。
|
|
|
|
|
|
|
|
|
|
|
|
### Telegram Bot で「Conflict: terminated by other getUpdates」と表示される
|
|
|
|
|
|
|
|
|
|
|
|
別のインスタンスが実行中の場合に発生します。`picoclaw gateway` が 1 つだけ実行されていることを確認してください。
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## 📝 API キー比較
|
|
|
|
|
|
|
|
|
|
|
|
| サービス | 無料枠 | ユースケース |
|
|
|
|
|
|
|---------|--------|------------|
|
|
|
|
|
|
| **OpenRouter** | 月 200K トークン | 複数モデル(Claude, GPT-4 など) |
|
2026-03-12 08:10:29 +00:00
|
|
|
|
| **Volcengine CodingPlan** | 9.9元/初月 | 中国ユーザーに最適、複数のSOTAモデル(Doubao、DeepSeek等) |
|
|
|
|
|
|
| **Zhipu** | 月 200K トークン | 中国ユーザーに適している |
|
2026-02-17 14:07:58 +00:00
|
|
|
|
| **Qwen** | 無料枠あり | 通義千問 (Qwen) |
|
2026-02-10 11:34:08 +00:00
|
|
|
|
| **Brave Search** | 月 2000 クエリ | Web 検索機能 |
|
2026-02-22 16:30:14 +00:00
|
|
|
|
| **Tavily** | 月 1000 クエリ | AI エージェント検索最適化 |
|
2026-02-10 11:34:08 +00:00
|
|
|
|
| **Groq** | 無料枠あり | 高速推論(Llama, Mixtral) |
|
2026-02-16 23:23:44 +00:00
|
|
|
|
| **Cerebras** | 無料枠あり | 高速推論(Llama, Qwen など) |
|
2026-03-13 06:02:23 +00:00
|
|
|
|
| **ModelScope** | 1 日 2000 リクエスト | 無料推論(Qwen, GLM, DeepSeek など) |
|
2026-03-12 08:10:29 +00:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
<div align="center">
|
|
|
|
|
|
<img src="assets/logo.jpg" alt="PicoClaw Meme" width="512">
|
|
|
|
|
|
</div>
|