@dp-pcs/ogp 0.2.0 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,8 +1,18 @@
1
1
  ---
2
2
  skill_name: ogp
3
- version: 0.1.0
4
- description: Manage OGP (Open Gateway Protocol) daemon and federation
5
- trigger: Use when the user wants to configure, start, or manage the OGP federation daemon
3
+ version: 0.2.0
4
+ description: Manage OGP (Open Gateway Protocol) daemon and federation. OGP adds peer-to-peer federation to OpenClaw, allowing AI agents to communicate across different deployments with cryptographic identity and signed messages.
5
+ trigger: Use when the user wants to configure, start, or manage the OGP federation daemon, manage federated peers, send messages to peers, or check federation status.
6
+ requires:
7
+ bins:
8
+ - ogp
9
+ state_paths:
10
+ - ~/.ogp/config.json
11
+ - ~/.ogp/peers.json
12
+ - ~/.ogp/daemon.pid
13
+ - ~/.ogp/keypair.json
14
+ install: npm install -g @dp-pcs/ogp
15
+ docs: https://github.com/dp-pcs/ogp
6
16
  ---
7
17
  ## Prerequisites
8
18
 
@@ -78,7 +78,7 @@ ogp federation list --status approved --json
78
78
  Example interaction:
79
79
  ```
80
80
  Select peers to configure:
81
- [x] Stanislav (giving-produces-microphone-mild.trycloudflare.com)
81
+ [x] Stanislav (peer-gateway.trycloudflare.com)
82
82
  [ ] Leonardo (leo-gateway.example.com)
83
83
  [x] Alice (alice.ngrok-free.app)
84
84
 
@@ -1,15 +1,41 @@
1
1
  ---
2
2
  skill_name: ogp-expose
3
- version: 0.1.0
4
- description: Expose OGP daemon via public tunnel (cloudflared/ngrok)
5
- trigger: Use when the user wants to expose their OGP daemon to the internet
3
+ version: 0.2.1
4
+ description: Expose OGP daemon via public tunnel (cloudflared/ngrok). Automates tunnel setup so federated peers can reach your gateway from anywhere on the internet, without exposing your real IP address.
5
+ trigger: Use when the user wants to expose their OGP daemon to the internet, get a public URL for federation, or set up a tunnel for peer discovery.
6
+ requires:
7
+ bins:
8
+ - ogp
9
+ optional_bins:
10
+ - cloudflared
11
+ - ngrok
12
+ state_paths:
13
+ - ~/.ogp/config.json
14
+ - ~/.ogp/tunnel.pid
15
+ - ~/.ogp/tunnel.log
16
+ install: npm install -g @dp-pcs/ogp
17
+ docs: https://github.com/dp-pcs/ogp
6
18
  ---
19
+
20
+ ## Security Note
21
+
22
+ **Tunnels are optional — and often more private than alternatives.**
23
+
24
+ `ogp expose` uses cloudflared or ngrok to create a secure public URL for your OGP daemon. This is one approach, not the only approach. You can expose your gateway however you prefer:
25
+
26
+ - **Cloudflared/ngrok tunnel** (default) — your real IP is never exposed; traffic routes through the tunnel provider's infrastructure
27
+ - **Reverse proxy** (nginx, Caddy, etc.) — if you have a server with a static IP
28
+ - **VPN/Tailscale** — federate only with peers on the same network
29
+ - **Any publicly reachable URL** — update `gatewayUrl` in `~/.ogp/config.json` manually
30
+
31
+ The tunnel approach is provided as a zero-config convenience. It installs no persistent services unless you explicitly run `ogp install` (which creates a LaunchAgent/systemd service and asks for confirmation first).
32
+
7
33
  ## Prerequisites
8
34
 
9
35
  The OGP daemon must be installed. If you see errors like 'ogp: command not found', install it first:
10
36
 
11
37
  ```bash
12
- npm install -g github:dp-pcs/ogp --ignore-scripts
38
+ npm install -g @dp-pcs/ogp
13
39
  ogp-install-skills
14
40
  ogp setup
15
41
  ```