An agentic development workflow, with memory

We deployed a dedicated agentic foundation on the client's server: an orchestrator scheduling recurring 24/7 jobs, a persistent long-term memory (dedicated MCP server), a knowledge graph of the ecosystem, reusable skills, and supervised autonomous sub-agents. Sourced RAG (chunking + embeddings + retrieval), completed by a graph + SQL layer. Rule: no source, no answer.

  • Orchestration (Dagster), long-term memory (MCP)
  • RAG: embeddings + knowledge graph + SQL
  • Extractor / Data Analyst / Reviewer sub-agent trio
  • OAuth2 read-only incremental connectors: Gmail, Drive, Odoo, TrackTik, Notion
  • Git versioning + auto-push, no-auto-send email guardrail

This foundation is built and operated with Claude Code : the same patterns ( memory, hooks, sub-agents, MCP ) we teach in our Claude & Claude Code training.

Tech Stack

Claude Code, Dagster, MCP memory, RAG (embeddings + graph + SQL), OAuth2, Git
An agent at the centre of a loop arrow, exchanging with a stack of records and linked to a knowledge graph

The challenge

Have AI agents work on real business tasks, continuously, with no context loss, no hallucination and never crossing a guardrail. A raw LLM answers from memory and invents; we needed a system that knows, cites its sources and stays under human control.

Result

An on-demand, multi-company data scientist and admin assistant that knows the context, cites its sources and stays accountable to a human.