convex-agents

Preserve AI agent context across sessions with Convex Agent components.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/qdhenry/Foundry-OSS --skill convex-agents-qdhenry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-agents
Source: https://github.com/qdhenry/Foundry-OSS/tree/main/.agents/skills/convex-agents
Command: npx skills add https://github.com/qdhenry/Foundry-OSS --skill convex-agents-qdhenry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preserve AI agent context across sessions.

Core Features & Use Cases

  • Persistent State - Conversation history survives restarts
  • Real-time Updates - Stream responses to clients automatically
  • Tool Execution - Run Convex functions as agent tools
  • Durable Workflows - Long-running agent tasks with reliability
  • Built-in RAG - Vector search for knowledge retrieval

Quick Start

Install the Convex agent package and initialize a simple agent to start a chat workflow.

Frequently Asked Questions about convex-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve AI agent context across sessions?

To preserve AI agent context across sessions, use a stateful agent framework that stores conversation history in a persistent database, ensuring threaded conversations survive application restarts automatically.

How do I build stateful AI agents with durable workflows?

Build stateful AI agents by integrating a backend platform that supports long-running workflows, streaming responses, and tool execution, allowing reliable task completion with built-in persistence and error handling.

Does this approach support streaming responses and tool integration?

Yes, stateful AI agents support streaming responses to update clients in real-time and allow tool integration by running backend functions directly within the agent workflow.

What's the best way to add RAG to AI agents?

The best way to add RAG to AI agents is using a backend with built-in vector search, enabling knowledge retrieval directly within the agent workflow for contextually accurate responses.

Do I need a specific LLM provider to manage threaded conversations?

Managing threaded conversations requires a compatible LLM provider alongside backend agent components that handle state persistence, ensuring conversation history remains intact across user sessions.

What are the limitations of stateful AI agents?

Limitations of stateful AI agents include the strict dependency on specific backend components and a compatible LLM provider, requiring proper error handling to manage long-running workflow failures.