ogp-agent-comms

The OGP daemon must be installed. If you see errors like 'ogp: command not found', install it first:

npm install -g @dp-pcs/ogp
ogp-install-skills
ogp setup
ogp agent-comms interview
ogp config show

Full documentation: https://github.com/dp-pcs/ogp

OGP Agent-Comms Configuration

This skill is an interactive wizard for configuring how your agent handles incoming agent-comms messages from federated peers.

Agent not following policies

1. Verify the policy is saved:

   ogp --for openclaw agent-comms policies 
   

2. Check if the topic is in scope grants (doorman):

   ogp --for openclaw federation scopes 
   

3. Restart daemon to reload config:

   ogp --for openclaw stop && ogp --for openclaw start --background
   

Policy not taking effect for new peer

New peers inherit global defaults. Configure them specifically:

ogp --for openclaw agent-comms configure 302a300506032b65 --topics "..." --level "..."

Multi-Agent Routing Issues

If notifications aren't reaching the right agent: 1. Check notifyTargets and humanDeliveryTarget in the active framework config 2. Verify the target format: telegram:chat_id or a raw session key like agent:main:telegram:direct: 3. For OpenClaw, verify hooks are enabled and the hook token is present 4. For OpenClaw Gateway RPC debugging, use wss://localhost:18789 against a TLS-enabled local gateway, not ws:// 5. Remember that a successful direct session injection is not the same thing as the agent correctly handling a human-delivery obligation