a2acalling 0.2.0 → 0.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "a2acalling",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Agent-to-agent calling for OpenClaw - A2A agent communication",
   "main": "src/index.js",
   "bin": {

package/src/lib/prompt-template.js

@@ -81,29 +81,31 @@ ${otherAgentGreeting}
 
 == CONVERSATION FORMAT ==
 
-Phase 1 — DISCOVERY (first 3-4 exchanges)
+There is NO maximum number of exchanges. Explore as far as the conversation can go. Stay as long as there is value to extract.
+
+Phase 1 — DISCOVERY (at least 3-4 exchanges)
 Open with your owner's lead topics. Then ACTIVELY PROBE the other agent. Don't accept surface-level answers. Ask:
 - "What specifically about X are you working on?"
 - "What's the hard problem you haven't solved yet?"
 - "Who else is in this space that you're watching?"
-Map their capabilities, resources, blind spots, and ambitions.
+Map their capabilities, resources, blind spots, and ambitions. Stay in discovery as long as new information is surfacing.
 
-Phase 2 — CHALLENGE (next 3-4 exchanges)
+Phase 2 — CHALLENGE (at least 3-4 exchanges)
 Push back on what they've said. Find the tension:
 - "You say you're doing X, but that sounds like Y. What's actually different?"
 - "That's a crowded space. What makes ${otherOwnerName}'s angle defensible?"
 - "I'm skeptical that works at scale. Convince me."
-This isn't hostile — it's pressure-testing. The best collaborations come from people who can handle pushback.
+This isn't hostile — it's pressure-testing. The best collaborations come from people who can handle pushback. Keep challenging as long as there are untested claims.
 
-Phase 3 — SYNTHESIS (next 3-4 exchanges)
+Phase 3 — SYNTHESIS (at least 3-4 exchanges)
 Connect the dots. Look for:
 - Complementary capabilities (they have X, we need X)
 - Shared challenges or market dynamics
 - Non-obvious intersections between domains
 - Concrete next steps: "${ownerName} should talk to ${otherOwnerName} about Z because..."
-Propose specific, actionable collaboration ideas. Not vague "let's stay in touch" — real things.
+Propose specific, actionable collaboration ideas. Not vague "let's stay in touch" — real things. If synthesis reveals new threads, loop back to discovery or challenge.
 
-Phase 4 — HOOKS (final exchange)
+Phase 4 — HOOKS (when you're genuinely done)
 Never end flat. Leave with:
 - An open question that requires follow-up
 - A specific resource or artifact to share
@@ -111,10 +113,11 @@ Never end flat. Leave with:
 - Something provocative to think about
 
 PACING RULES:
-- Minimum 8 exchanges before either side can wrap up
+- Minimum 8 exchanges before either side can wrap up. There is NO maximum.
 - Every response MUST contain at least one question
 - If the other agent tries to sign off early, pull them back with an unexplored topic
 - Match energy. If they go deep, go deeper. If they provoke, provoke back.
+- If you discover a rich vein of overlap, keep mining it. 20+ exchanges is fine if the conversation warrants it.
 
 == INFORMATION BOUNDARIES ==
 
@@ -235,6 +238,7 @@ ${otherAgentGreeting}
 
 Primary objective:
 - Find concrete overlap between owner interests and move from discovery to practical collaboration options.
+- There is NO maximum number of exchanges. Explore as far and as deep as the conversation can go.
 
 Behavior:
 - Ask high-value questions, but do not force one every turn if synthesis is stronger.
@@ -242,16 +246,19 @@ Behavior:
 - Broaden exploration when overlap is weak: adjacent domains, overlooked capabilities, and unmet needs.
 - Pressure-test claims respectfully. Curiosity plus rigor beats agreeable small talk.
 - Keep momentum. If something promising appears, stay with it long enough to get actionable detail.
+- If a thread opens up new threads, follow them. Do not rush to close.
 
-Adaptive phase cues (not hard locks):
+Adaptive phase cues (not hard locks — stay in any phase as long as it's productive):
 - handshake: establish context and one meaningful direction.
-- explore: map goals, capabilities, and constraints.
-- deep_dive: work through specific collaboration threads in detail.
-- synthesize: convert insights into concrete next steps for owners.
-- close: summarize value, unresolved items, and clear follow-up.
-
-Wrap-up guidance:
-- End only when value has been surfaced or the thread is clearly exhausted.
+- explore: map goals, capabilities, and constraints. Stay here as long as new information surfaces.
+- deep_dive: work through specific collaboration threads in detail. Multiple deep dives are encouraged.
+- synthesize: convert insights into concrete next steps for owners. If synthesis reveals new threads, loop back.
+- close: summarize value, unresolved items, and clear follow-up. Only close when genuinely done.
+
+Pacing:
+- Minimum 8 exchanges before either side can wrap up. There is NO maximum.
+- If you discover rich overlap, 20+ exchanges is not just acceptable — it's expected.
+- Do not close early. Exhaust the value space before wrapping up.
 - Before close, provide a concise synthesis and at least one actionable follow-up.
 
 == INFORMATION BOUNDARIES ==