lattice-pns avatar

hermes-agent-pns

0 subscribers
PythonTeXBibTeX Style

The agent that grows with you

Live activities

We've implemented tracking for the last received Server-Sent Event (SSE) ID in our Lattice platform gateway. By including this ID in the Last-Event-ID header during reconnect attempts, the server can now reliably replay any events missed during temporary connection drops. This ensures a smoother, more resilient experience for event-driven workflows.

Reliable server connection

We removed an explicit catch block for asyncio.CancelledError in the Lattice platform gateway's SSE listener. By allowing the cancellation signal to propagate instead of forcefully breaking, we ensure the task handles shutdown more predictably. This change cleans up our task lifecycle management. Handling errors

This refactor centralizes Lattice Ed25519 authentication logic into a single lattice_auth module, cleaning up redundant code in both the platform adapter and the tools layer. Additionally, it exposes a new lattice_get_pubkey tool, allowing agents to easily retrieve and share their public key for messaging. These changes streamline the agent communication stack while simplifying future maintenance.

Updated the message processing logic in LatticeAdapter to use a more explicit prompt when relaying inbound notifications to the user. This ensures the agent correctly identifies incoming content as external messages and handles the notification relay flow without mistakenly treating it as a direct user query.

Previously, unhandled errors during message processing—such as those occurring within extract_media or the handler itself—would fail silently, leaving users with no feedback beyond a stalled typing indicator. We've updated the gateway's outer exception handler to catch these errors and propagate the type and a brief description back to the user chat. This provides much-needed visibility into request failures, ensuring users aren't left waiting for messages that will never arrive. Debugging frustration

This update changes how Lattice events are handled by routing them directly to the main platform session instead of treating them as a separate, non-repliable thread. By dynamically selecting a target platform—prioritizing configured home channels or allowlist users—the agent can now seamlessly reply to Lattice notifications within the user's active conversation. This improves UX by enabling fluid, context-aware responses to Lattice-based events.

Updated the Lattice platform adapter to provide clearer behavioral instructions to the AI when receiving agent-to-agent messages. These adjustments to the system prompt help the model distinguish between direct user interaction and automated messages, ensuring more accurate handling of notifications from external agents.

The Lattice platform adapter node has been updated to directly invoke the internal _message_handler for processing incoming notifications, rather than relying on the higher-level handle_message method. This simplifies the event dispatch flow for Lattice-specific messages.

Updated _process_notification in the Lattice platform to use the base handle_message method instead of the direct _message_handler. This change ensures that agent responses are correctly routed through _process_message_background, which properly handles sending responses back to the original source. This improves reliability for downstream communication flows. Developer fixing a bug

This update introduces agent-to-agent communication capabilities by adding a new lattice_send_agent tool. It includes a robust authentication mechanism using Ed25519 signing for secure /send requests to the Lattice platform. Notifications received via Lattice are now automatically formatted with context to help the AI recognize incoming machine-to-machine communications. Agent communication

This update improves the UX for users setting up Lattice by automatically displaying the generated Ed25519 public key in the terminal immediately following a successful configuration. This makes it significantly easier for users to identify and register their key with their Lattice server without digging through initialization logs. The implementation adds a helper to retrieve the key securely and updates both the gateway and the CLI setup flow to handle the display.

This update integrates Lattice as a supported platform for push notifications within the Hermes gateway. Users can now easily configure their Lattice server URL and subscription topics directly through the CLI setup wizard. This enhancement streamlines the deployment of Lattice-based SSE notifications, including automatic Ed25519 keypair generation on the first connection.

This update moves the project to the new lattice-pns repository, updating all installation scripts, documentation links, and internal configuration references accordingly. The codebase remains functional, simply pointing to the new official home for future updates and development.

Added support for the Lattice platform, enabling push notifications via SSE. This integration includes a dedicated LatticeAdapter, Ed25519 key authentication, and configurable topic subscriptions within the existing messaging framework. This update expands connectivity options for the gateway and enhances real-time communication capabilities. Integration challenge

- End of feed -