agent protocol and web hooks
Message 1 of 3: Overview
The v2 zip introduces a completely new agent context structure with:
1. Shared workflow contract (shared/WORKFLOW_CONTRACT.md) - enforces rules across all agents
2. New handshake protocol (TRIGGERS.md files) - structured Telegram triggers for auto-spawning
3. Context-based architecture - SOUL.md, AGENTS.md, IDENTITY.md, USER.md, TOOLS.md per agent
4. Enhanced contracts - "Agent Handshake Protocol" with numbered steps in spawn tasks
The current system uses a config-based structure (auth-profiles.json, models.json) with webhook → Gateway hooks → agent spawn (no Telegram triggers).
Key Compatibility Concerns
1. Handshake Protocol vs. Webhook Flow
Current flow:
Trello → Webhook Server (port 3003) → Gateway /hooks/agent → Agent spawn
v2 TRIGGERS.md expects:
Telegram message with emoji trigger (e.g., "
TRIGGER: Coding Agent") → Agent spawns subagent
Question for Krill:
• Does the webhook server need to generate Telegram messages with these trigger formats after processing Trello webhooks?
• Or should the webhook server spawn agents directly and bypass the Telegram trigger layer?
• Is the handshake protocol intended to replace the current webhook→agent flow, or augment it?
2. Path Resolution for shared/WORKFLOW_CONTRACT.md
The v2 zip introduces a completely new agent context structure with:
1. Shared workflow contract (shared/WORKFLOW_CONTRACT.md) - enforces rules across all agents
2. New handshake protocol (TRIGGERS.md files) - structured Telegram triggers for auto-spawning
3. Context-based architecture - SOUL.md, AGENTS.md, IDENTITY.md, USER.md, TOOLS.md per agent
4. Enhanced contracts - "Agent Handshake Protocol" with numbered steps in spawn tasks
The current system uses a config-based structure (auth-profiles.json, models.json) with webhook → Gateway hooks → agent spawn (no Telegram triggers).
Key Compatibility Concerns
1. Handshake Protocol vs. Webhook Flow
Current flow:
Trello → Webhook Server (port 3003) → Gateway /hooks/agent → Agent spawn
v2 TRIGGERS.md expects:
Telegram message with emoji trigger (e.g., "
TRIGGER: Coding Agent") → Agent spawns subagentQuestion for Krill:
• Does the webhook server need to generate Telegram messages with these trigger formats after processing Trello webhooks?
• Or should the webhook server spawn agents directly and bypass the Telegram trigger layer?
• Is the handshake protocol intended to replace the current webhook→agent flow, or augment it?
2. Path Resolution for shared/WORKFLOW_CONTRACT.md
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
