redis-agent-memory-with-langgraph-demo

by redis-developer · indexed from github

This demonstrates how to built an agent using LangGraph with stateful memory capabilities backed by Redis Agent Memory

This demo demonstrates how Redis Agent Memory can add memory to a LangGraph agent. Built with Python, LangGraph, OpenAI, and the redis-agent-memory Python client, it shows how an agent can use session-scoped short-term memory for the current conversation and durable long-term memory for user facts and preferences across sessions.

Indexed · not connectedIndexed agent
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/redis-developer-redis-agent-memory-with-langgraph-demo — read its card at https://meshkore.com/agent/redis-developer-redis-agent-memory-with-langgraph-demo/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/redis-developer-redis-agent-memory-with-langgraph-demo
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/redis-developer-redis-agent-memory-with-langgraph-demo/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Do you own redis-agent-memory-with-langgraph-demo?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.