Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,10 @@ build-all: generate
GOOS=windows GOARCH=amd64 $(GO) build $(LDFLAGS) -o $(BUILD_DIR)/$(BINARY_NAME)-windows-amd64.exe ./$(CMD_DIR)
@echo "All builds complete"

## build-signal: Build the picoclaw-signal-bridge daemon
build-signal:
@cd contrib/picoclaw-signal-bridge && ./build.sh

## install: Install picoclaw to system and copy builtin skills
install: build
@echo "Installing $(BINARY_NAME)..."
Expand Down
51 changes: 51 additions & 0 deletions README.fr.md
Original file line number Diff line number Diff line change
Expand Up @@ -272,6 +272,7 @@ Discutez avec votre PicoClaw via Telegram, Discord, DingTalk, LINE ou WeCom
| **DingTalk** | Moyen (identifiants de l'application) |
| **LINE** | Moyen (identifiants + URL de webhook) |
| **WeCom** | Moyen (CorpID + configuration webhook) |
| **Signal** | Moyen (démon bridge autonome) |

<details>
<summary><b>Telegram</b> (Recommandé)</summary>
Expand Down Expand Up @@ -552,6 +553,56 @@ picoclaw gateway

</details>

<details>
<summary><b>Signal</b> (Sécurité Maximale)</summary>

PicoClaw prend en charge Signal via un démon bridge autonome natif pour une confidentialité et une sécurité maximales.

**1. Compiler le Signal Bridge**

Consultez les [instructions de picoclaw-signal-bridge](contrib/picoclaw-signal-bridge/README.md) pour compiler le démon, ou exécutez simplement :
```bash
make build-signal
```

**2. Lier votre Appareil**

```bash
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --link --data-dir ~/.picoclaw/signal
```

**3. Configurer PicoClaw**

```json
{
"channels": {
"signal": {
"enabled": true,
"bridge_url": "unix:///tmp/picoclaw-signal.sock",
"allow_from": ["+1234567890"]
}
}
}
```

> **Astuce UX :** Le bridge extrait automatiquement les numéros de téléphone E164, vous permettant de les configurer facilement dans `allow_from` au lieu de gérer des UUID complexes.

**4. Lancer**

Démarrez à la fois le bridge et PicoClaw :

```bash
# Terminal 1 : Exécuter le bridge
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --data-dir ~/.picoclaw/signal --socket /tmp/picoclaw-signal.sock

# Terminal 2 : Exécuter PicoClaw
picoclaw gateway
```

</details>

## <img src="assets/clawdchat-icon.png" width="24" height="24" alt="ClawdChat"> Rejoignez le Réseau Social d'Agents

Connectez PicoClaw au Réseau Social d'Agents simplement en envoyant un seul message via le CLI ou n'importe quelle application de chat intégrée.
Expand Down
51 changes: 51 additions & 0 deletions README.ja.md
Original file line number Diff line number Diff line change
Expand Up @@ -236,6 +236,7 @@ Telegram、Discord、QQ、DingTalk、LINE、WeCom で PicoClaw と会話でき
| **DingTalk** | 普通(アプリ認証情報) |
| **LINE** | 普通(認証情報 + Webhook URL) |
| **WeCom** | 普通(CorpID + Webhook設定) |
| **Signal** | 普通(独立した bridge デーモン) |

<details>
<summary><b>Telegram</b>(推奨)</summary>
Expand Down Expand Up @@ -512,6 +513,56 @@ picoclaw gateway

</details>

<details>
<summary><b>Signal</b>(最高水準のセキュリティ)</summary>

PicoClaw は、ネイティブの独立した bridge デーモンを通じて Signal をサポートし、最大限のプライバシーとセキュリティを確保します。

**1. Signal Bridge のビルド**

ビルドの詳細については [picoclaw-signal-bridge の手順](contrib/picoclaw-signal-bridge/README.md) を参照するか、以下を実行してください:
```bash
make build-signal
```

**2. デバイスのリンク**

```bash
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --link --data-dir ~/.picoclaw/signal
```

**3. PicoClaw の設定**

```json
{
"channels": {
"signal": {
"enabled": true,
"bridge_url": "unix:///tmp/picoclaw-signal.sock",
"allow_from": ["+1234567890"]
}
}
}
```

> **UX のヒント:** ブリッジは自動的に E164 電話番号を抽出するため、複雑な UUID ではなく、電話番号を 直接 `allow_from` に設定できます。

**4. 実行**

bridge と PicoClaw の両方を起動します:

```bash
# Terminal 1: bridge を実行
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --data-dir ~/.picoclaw/signal --socket /tmp/picoclaw-signal.sock

# Terminal 2: PicoClaw を実行
picoclaw gateway
```

</details>

## ⚙️ 設定

設定ファイル: `~/.picoclaw/config.json`
Expand Down
51 changes: 51 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -274,6 +274,7 @@ Talk to your picoclaw through Telegram, Discord, DingTalk, LINE, or WeCom
| **DingTalk** | Medium (app credentials) |
| **LINE** | Medium (credentials + webhook URL) |
| **WeCom** | Medium (CorpID + webhook setup) |
| **Signal** | Medium (standalone bridge daemon) |

<details>
<summary><b>Telegram</b> (Recommended)</summary>
Expand Down Expand Up @@ -559,6 +560,56 @@ picoclaw gateway

</details>

<details>
<summary><b>Signal</b> (Extremely Secure)</summary>

PicoClaw supports Signal via a native standalone bridge daemon for maximum privacy and security.

**1. Build the Signal Bridge**

See the [picoclaw-signal-bridge instructions](contrib/picoclaw-signal-bridge/README.md) or simply run:
```bash
make build-signal
```

**2. Link your Device**

```bash
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --link --data-dir ~/.picoclaw/signal
```

**3. Configure PicoClaw**

```json
{
"channels": {
"signal": {
"enabled": true,
"bridge_url": "unix:///tmp/picoclaw-signal.sock",
"allow_from": ["+1234567890"]
}
}
}
```

> **UX Tip:** The bridge automatically extracts E164 phone numbers, allowing you to easily configure phone numbers in `allow_from` rather than dealing with complex UUIDs.

**4. Run**

Start both the bridge and PicoClaw:

```bash
# Terminal 1: Run the bridge
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --data-dir ~/.picoclaw/signal --socket /tmp/picoclaw-signal.sock

# Terminal 2: Run PicoClaw
picoclaw gateway
```

</details>

## <img src="assets/clawdchat-icon.png" width="24" height="24" alt="ClawdChat"> Join the Agent Social Network

Connect Picoclaw to the Agent Social Network simply by sending a single message via the CLI or any integrated Chat App.
Expand Down
51 changes: 51 additions & 0 deletions README.pt-br.md
Original file line number Diff line number Diff line change
Expand Up @@ -273,6 +273,7 @@ Converse com seu PicoClaw via Telegram, Discord, DingTalk, LINE ou WeCom.
| **DingTalk** | Médio (credenciais do app) |
| **LINE** | Médio (credenciais + webhook URL) |
| **WeCom** | Médio (CorpID + configuração webhook) |
| **Signal** | Médio (daemon bridge autônomo) |

<details>
<summary><b>Telegram</b> (Recomendado)</summary>
Expand Down Expand Up @@ -553,6 +554,56 @@ picoclaw gateway

</details>

<details>
<summary><b>Signal</b> (Segurança Máxima)</summary>

O PicoClaw suporta o Signal através de um daemon bridge autônomo nativo para máxima privacidade e segurança.

**1. Construir o Signal Bridge**

Veja as [instruções do picoclaw-signal-bridge](contrib/picoclaw-signal-bridge/README.md) para construir o daemon, ou simplesmente execute:
```bash
make build-signal
```

**2. Vincular seu Dispositivo**

```bash
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --link --data-dir ~/.picoclaw/signal
```

**3. Configurar o PicoClaw**

```json
{
"channels": {
"signal": {
"enabled": true,
"bridge_url": "unix:///tmp/picoclaw-signal.sock",
"allow_from": ["+1234567890"]
}
}
}
```

> **Dica de UX:** A bridge extrai automaticamente números de telefone E164, permitindo que você os configure facilmente no `allow_from` em vez de lidar com UUIDs complexos.

**4. Executar**

Inicie a bridge e o PicoClaw:

```bash
# Terminal 1: Executar a bridge
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --data-dir ~/.picoclaw/signal --socket /tmp/picoclaw-signal.sock

# Terminal 2: Executar o PicoClaw
picoclaw gateway
```

</details>

## <img src="assets/clawdchat-icon.png" width="24" height="24" alt="ClawdChat"> Junte-se a Rede Social de Agentes

Conecte o PicoClaw a Rede Social de Agentes simplesmente enviando uma única mensagem via CLI ou qualquer App de Chat integrado.
Expand Down
51 changes: 51 additions & 0 deletions README.vi.md
Original file line number Diff line number Diff line change
Expand Up @@ -253,6 +253,7 @@ Trò chuyện với PicoClaw qua Telegram, Discord, DingTalk, LINE hoặc WeCom.
| **DingTalk** | Trung bình (app credentials) |
| **LINE** | Trung bình (credentials + webhook URL) |
| **WeCom** | Trung bình (CorpID + cấu hình webhook) |
| **Signal** | Trung bình (standalone bridge daemon) |

<details>
<summary><b>Telegram</b> (Khuyên dùng)</summary>
Expand Down Expand Up @@ -533,6 +534,56 @@ picoclaw gateway

</details>

<details>
<summary><b>Signal</b> (Bảo mật tối đa)</summary>

PicoClaw hỗ trợ Signal thông qua một trình nền (daemon) bridge độc lập, giúp tối đa hoá sự riêng tư và bảo mật.

**1. Biên dịch (Build) Signal Bridge**

Xem [hướng dẫn picoclaw-signal-bridge](contrib/picoclaw-signal-bridge/README.md) để build daemon, hoặc đơn giản chạy lệnh:
```bash
make build-signal
```

**2. Liên kết Thiết bị**

```bash
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --link --data-dir ~/.picoclaw/signal
```

**3. Cấu hình PicoClaw**

```json
{
"channels": {
"signal": {
"enabled": true,
"bridge_url": "unix:///tmp/picoclaw-signal.sock",
"allow_from": ["+1234567890"]
}
}
}
```

> **Mẹo UX:** Bridge tự động trích xuất số điện thoại định dạng chuẩn (E164), cho phép bạn dễ dàng cấp quyền bằng số điện thoại trong `allow_from` thay vì phải xử lý các chuỗi UUID phức tạp.

**4. Khởi động**

Khởi động đồng thời cả bridge và mạng PicoClaw:

```bash
# Terminal 1: Chạy bridge
cd contrib/picoclaw-signal-bridge
./picoclaw-signal-bridge --data-dir ~/.picoclaw/signal --socket /tmp/picoclaw-signal.sock

# Terminal 2: Chạy PicoClaw
picoclaw gateway
```

</details>

## <img src="assets/clawdchat-icon.png" width="24" height="24" alt="ClawdChat"> Tham gia Mạng xã hội Agent

Kết nối PicoClaw với Mạng xã hội Agent chỉ bằng cách gửi một tin nhắn qua CLI hoặc bất kỳ ứng dụng Chat nào đã tích hợp.
Expand Down
Loading
Loading