Person
Merbin J Anselm
Capabilities
Provides
Agent toolingCAPAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.Retrieval-augmented generationCAPRetrieval-augmented generationGrounding a model's answer in data retrieved at question time: text split into chunks, each chunk embedded as a vector, and the chunks nearest to the question placed into the prompt. Semantic search is the same retrieval with a person reading the matches, and fine-tuning changes the model's weights, not its input.
Entries
Group by
EntrySignals
Maintains
@mi8y/cap-agents-aicore-vectorstore@mi8y/cap-agents-aicore-vectorstoreA LangChain vector store backed by SAP AI Core Document Grounding: the collection holds the documents and makes the embeddings, and the CAP application stores no vectors of its own.independent, cap
LangChain vector store on SAP AI Core Document Grounding
@mi8y/cap-agents-cds-vectorstore@mi8y/cap-agents-cds-vectorstoreA LangChain vector store whose documents and embeddings are CDS entities, so retrieval runs as a CDS query against the database the CAP service is already bound to.independent, cap
LangChain vector store with CDS entities for embeddings
@mi8y/cap-agents-memory@mi8y/cap-agents-memoryA LangGraph Store written against CDS: the facts and preferences an agent keeps between sessions are entities in the CAP database, read and written inside a request handler under its tenant.independent, cap
LangGraph Store keeping agent memory as CDS entities
@mi8y/cap-agents-sdm-backend@mi8y/cap-agents-sdm-backendA Deep Agents filesystem backend whose files are documents in an SAP Document Management repository, so what a CAP agent reads and writes stays where people can open it too.independent, cap
Not a way to edit Office formats: the author states that access to a file does not automatically provide native editing of Word documents, spreadsheets or PDFs, and suggests starting with text-based content such as instructions, templates and reports. Not a control point either: a prompt telling the agent to ask for confirmation or to leave a template alone needs enforceable application controls where that is a business requirement, and the host application stays responsible for the authenticated request context and tenant isolation.
Deep Agents filesystem over an SAP Document Management repository
@mi8y/cds-langgraph-persistence@mi8y/cds-langgraph-persistenceA LangGraph checkpointer backed by CDS, so an agent's state survives the request that created it — durability for LangChain and LangGraph agents running inside the CAP Node.js runtime.independent, cap
LangGraph checkpointer backed by CDS for CAP agents
Maintains: samples, sketches and references
Reports Assistant with SAP Document ManagementReports Assistant with SAP Document ManagementA CAP agent that turns a few notes into a status report and saves it in an SAP Document Management repository, where the instructions and the skills it follows are kept too.independent, cap
CAP agent writing reports into a shared SDM document workspace
Details
History
- @mi8y/cap-agents-memorycapability:agent-tooling declared four comparison properties on 2026-10-15. Three are answered from the README's own opening and CAP notes, re-read the same day and unchanged, scoped to the node flavor: the package holds state between turns, it is written against LangGraph's Store API, and that state is rows in the CAP database under the request's tenant. The approval property is left out: the README says nothing about it.
- @mi8y/cds-langgraph-persistenceThe entry stated the capability with nothing behind it while the README says exactly what the package holds. Read on 2026-10-15: checkpoints are short-term, thread-scoped state used to resume workflows, retain conversation history and support time travel, backed by CDS, requiring @sap/cds >= 10. capability:agent-tooling declared its comparison properties the same day, so the edge now answers three of them, scoped to the node flavor. The README's sentence about what to prefer for a new application has been reworded since 2026-09-21 — it now reads 'This package remains available for its existing CDS checkpointer implementation' — and the claim the page already carries is unchanged, so only the quote on the edge is new.
- @mi8y/cap-agents-memoryThe announcement post of 2026-09-22 states what the package is an add-on to, which the entry named only as a neighbour that had since gained a checkpointer: 'The package is designed as an add-on for @cap-js/agents and extends it with a persistence layer for application-defined memories that can be shared across agent conversations', and 'The CAP Agent runtime still provides the model, generated tools, system prompt, middleware, A2A endpoint, and checkpointing. The memory add-on contributes only the cross-session Store and the tools that use it.' The same post dates the older package's position, 'I explained ... And went on to introduce the @mi8y/cds-langgraph-persistence plugin for durable state management within CAP agents. But it's already obsolete by now, as CAP itself has a built-in Checkpointer mechanism.' The README's line on which CAP database adapters the CDS queries run against had been left out. Both post quotes and the adapter line are now on the provides edge. Re-read on 2026-09-23 and unchanged: the repository, the MIT licence, the '@sap/cds >= 10' and '@langchain/core >= 1' peer dependencies, the generated entities, the Store operations and the Vector(1536) field.
- @mi8y/cds-langgraph-persistenceThe standalone repository was renamed: GitHub's API resolves mi8y/cds-langgraph-persistence to mi8y/cap-agents-addons, and the package now sits under packages/ beside cap-agents-memory, cap-agents-cds-vectorstore and cap-agents-aicore-vectorstore. Its own package.json points at the new repository.
- @mi8y/cds-langgraph-persistenceThe package README states 'Requires `@sap/cds >= 10`' and package.json 0.7.0 declares the same peer dependency, with peerDependenciesMeta marking it not optional. The old range predates the move into the monorepo.
- @mi8y/cds-langgraph-persistenceThe maintainer marked the package deprecated for new applications, which the page said nowhere: the repository README reads '**Deprecated for new applications:** [`@cap-js/agents`](https://github.com/cap-js/agents) now includes checkpointer support. Prefer it for new CAP agent applications; this package remains available for existing implementations.' Reported as the maintainer's dated statement, not as a reading of ours, and the entry keeps its page, its edges and its readings.
- First entry seenDiscovered via Added by hand, SAP Community, npm registry, SAP Community · cap-tag.
Profile
For your agent
- Ref
actor:anselm94- JSON
- /actors/anselm94.json
- MCP
- Connecting an agent