sessions
to handle the context and state of the agent.
sessions
are an incredibly powerful feature in the Mamga ecosytem because testing and optimizing agents requires accessing the unique instances of your agent. With sessions
, you can snapshot different states, contexts, and interactions of your agent.
A new session is created when a hook
is triggered with a new session id
, or when the agent is accessed via the agent api
with a new session id
.
When one of these events is triggered without a session id
, a new temporary session is created to handle the agent interactions.
agent api
is a way to interact with the agent via websocket or http requests.
When using the agent api
, you can specify a session id
to interact with a specific session of the agent.
HTTP Request
You can specify the session id
as a field in the body of the request when accessing your agent via the /chat
route.
session id
using a query parameter.
wss://api.magmadeploy.com/v1?agent_id=<agent_id>&api_key=<agent_public_api_key>&sessionId=<session_id>
If you are triggering a connection from a service that does not allow you to add query parameters, you can convert them to key=value path parameters
wss://api.magmadeploy.com/v1/agentId=<agent_id>/apiKey=<agent_public_api_key>/sessionId=<session_id>
sessionId
that matches req.body.userId
.
See Hook Advanced Usage for more details