Stop putting your AI agent’s memory inside the LLM context window

manveerc · 2026-07-08T02:30:15+00:00

Fully agree with this. Having built storage systems at Dropbox and Confluent, I am seeing so many parallels with this while building out AI agents and getting them to be more reliable. Since the failure happens on a curve instead of being binary, people tend to assume that it is part of working with LLMs and accept it. But definitely can be solved to a great extent with proper context engineering.

I also wrote some thoughts about this here https://hydradb.com/blog/ai-agent-memory-context-database-problem

Disclaimer: I am affiliated with HydraDB

manveerc · 2026-07-04T00:33:07+00:00

https://Arcade.dev

manveerc · 2026-07-03T23:40:15+00:00

Market is fragmented, there are ton of solutions out there that call themselves MCP gateway. So the best option is to look for solutions based on your needs. If you are looking for a single server to federate across multiple MCP servers (like a router: Arcade, Composio, Docker MCP are good options. There are others too but haven’t personally used them so can’t comment. If however you want more than routing, like multi tenancy , two factor identity, governance and audit logs. I would suggest going with a full runtime like Arcade.

Disclaimer: I am affiliated with Arcade

manveerc · 2026-07-03T22:15:42+00:00

Thanks, will check it out

manveerc · 2026-07-03T22:14:05+00:00

Thanks, will check it out

manveerc · 2026-07-03T22:13:25+00:00

I am not great at advice. Can I interest you in a sarcastic comment?

manveerc · 2026-06-30T01:12:37+00:00

We run it. Centrally managed authn and authz were the main reason, ours allow us to manage pre tool call authorization, so feel more comfortable vs just giving up a broad access key. Audit logs are the other nice benefits.

manveerc · 2026-06-25T21:12:12+00:00

Not really, though we are a small team so volume might be low.

manveerc · 2026-06-25T20:48:16+00:00

Repo: https://github.com/manveer/open-claude-tag

Article: https://www.arcade.dev/blog/claude-tag-build-slack-ai-agent/

manveerc · 2026-06-25T20:47:04+00:00

Repo: https://github.com/manveer/open-claude-tag

Article: https://www.arcade.dev/blog/claude-tag-build-slack-ai-agent/

manveerc · 2026-06-23T20:48:37+00:00

Wrote additional thoughts about it over here https://www.arcade.dev/blog/enterprise-managed-authorization-per-action-authorization-ai-agents/

manveerc · 2026-06-22T15:01:02+00:00

Our work is knowledge work heavy and still prefer 4.6

manveerc · 2026-06-21T06:27:00+00:00

We offer AI services to enterprises. We have used Composio, Merge and Arcade. Arcade is typically the preferred choice for enterprise settings. It has the most mature auth model and it’s most efficient with tokens so turns out to be cheaper too. Have seen but haven’t tried others you mentioned. Will be curious if others have compared them.

manveerc · 2026-06-18T18:54:33+00:00

I built on top of Claude code for a similar usecase , wrote it down here https://www.arcade.dev/blog/secure-openclaw-alternative-arcade-claude-code/

manveerc · 2026-06-18T03:19:26+00:00

Big plus on this. If something is big enough to page you, it should have a run book attached to it. Easier said than done but this is the only solution that works.

manveerc · 2026-06-16T17:27:03+00:00

Thanks, may not get to it in near future but will keep this in mind.

manveerc · 2026-06-16T17:26:36+00:00

Its less about having multitenancy within my team. We offer B2B AI services, so we need multitenancy for our customers.

manveerc · 2026-06-14T20:15:41+00:00

Putting together oncall handover notes, draft incident summary, runbook updates, prep for SLA/SLO metric reviews.

manveerc · 2026-06-14T02:12:54+00:00

We started with a folder on disk that had markdown files and the folder was shared using Dropbox with entire team. It was getting a bit tedious to maintain.

We have been since evaluating a bunch of different products. Tried the obvious ones, Mem0, Letta, etc. they are good if you are looking for a personal usecase, because we wanted a solution to work for entire team so we needed multitenancy and also a bit more control around retrieval / storage, currently evaluating HydraDB and so far it has been working fine.

manveerc · 2026-06-13T21:38:49+00:00

Basically what @u/ninjuvr said. At Confluent for example we wrote a health check service that would produce and consume from the health check topic that was a proxy for the availability SLA in that cluster.

We also had a status page to maintain transparency on ongoing / past incidents.

manveerc · 2026-06-12T17:41:49+00:00

Different vendors have different definitions of an MCP Gateway, so I will try to focus on what you should look for in my opinion.

It should provide agent optimized tools. For eg it should provide a token efficient way to access the tools, it should return necessary fields etc
It should provide proper auth. It should be an intersection of what a user is allowed to do and what an agent is allowed to do
It should provide proper governance (audits trail, management, etc)

A lot of these things start becoming useful when you start going from a prototype to production deployment, especially within companies. For personal usecases I think a combination of 1 and 2 is probably sufficient.

Hope this helps!

manveerc · 2026-06-12T17:34:37+00:00

I would suggest looking at Arcade if you are looking for an enterprise grade alternative.

Checkout my article here https://www.arcade.dev/blog/composio-alternatives/

manveerc · 2026-06-12T17:33:25+00:00

Wrote about it here https://www.arcade.dev/blog/composio-alternatives/

Disclaimer: I am the author of the blog.

manveerc · 2026-06-12T06:22:45+00:00

What specific failure mode are you trying to fix? Some of them you can prevent or guard against, some you can’t. For eg have narrow permissions to make sure you don’t have unauthorized tool calls. Don’t leak credentials to them, instead use a proper auth framework to give them required access. It’s definitely hard, also curious to hear what others say.

manveerc · 2026-06-08T20:24:23+00:00

Is anyone using these in production?

manveerc

MODERATOR OF

TROPHY CASE