AI Travel Planner - April 10, 2025 - Tripmate - PLDG 2

[Nkovaturient]

Contributors

@Dhruv-Varshney-developer @Nkovaturient

Accomplished Tasks

1. WebSocket Client in Eliza (wsClient.ts):

   • Connects to ws://localhost:8765
   • Sends user messages to TripMate
   • Listens for TripMate's response and forwards it via Eliza's runtime handler callback

2. WebSocket Server in TripMate:

• Accepts connection from Eliza
• Receives user messages, routes them into the TripMate agent
• Forwards TripMate’s responses back to Eliza via the WebSocket

3. Dynamic Callback Binding:

   • connectWebServer(callback) ensures messages from TripMate are routed to the right conversation context using HandlerCallback

4. Unified storeTripData Action:

   • Registered once in Eliza to handle message routing (storeTripData, sendToTripMate) based on content pattern match
   • Eliminates issues with multiple independent actions not firing

5. Initiated work on Agent-3 and ElizaOS Client is ready for Agent-3.

Update

• ✅Agent 1 and Agent 2 sync and connected successfully
• ✅ Storacha Upload and data storage
• ✅ Enables real-time agent collaboration
• ✅ We’ve started building Agent-3, an interaction layer for Tripmate. Agent-3 can view final trip details stored in Storacha, and presents them in a shareable format to family and friends. They can interact directly with Agent-3, ask questions, view plans, and leave comments or suggestions.
• ✅All feedback is stored back in Storacha and can be retrieved by Agent-1, enabling a seamless feedback loop and collaborative planning experience.

Demo Videos

TripMate.Agent.Sync.Final-VEED.mp4

Questions

1. Process of architectural options for UCAN delegation to Agent3, client-owned/user/delegated would be best?

• https://docs.storacha.network/concepts/architecture-options/
• https://docs.storacha.network/concepts/ucans-and-storacha/

2. For multi users purpose advancements, should there be separate, independent spaces as per the user, in that case, upload architectural options should be user-owned , then our users could delegate capabilities for their space to our backend application(Agent1) or share spaces(Agent3) between friends by delegating to each other?

Next Tasks

Dhruv:

• RAG implementation in agent-3
• Final documentation
• Pushing everything to production via Railway

Neha:

• Connect to Storacha using UCANs
• Retrieve from agent-1
• Present this info in a Telegram-friendly format (Simple Eliza Agent)
• Enable interactions from family/friends: View travel Plans
• Store all interactions back to Storacha