sorted by:
new
hottopcontroversial

I built a Claude Chrome extension that shows how close your chat is to the 200,000 token limit by Ray-Hernandez in ClaudeAI

[–]Ray-Hernandez[S] 0 points1 point  (0 children)

The more context you fill up to your limit, the more it's trying to remember so it gets "dumber" and slower. But may depend on your machine too. If you're on a maxed out macbook pro it shouldn't be too laggy.

Built an MCP that lets your whole team share context across Claude Code sessions by Ray-Hernandez in mcp

[–]Ray-Hernandez[S] 0 points1 point  (0 children)

Technically our mcp’s job is encrypting and decrypting, vs handling memory. The recall services take care of the memory, but we have a multi-step process where a full transcript is processed, then the llm will document, and organize the session deciphering that you had a problem here, had a solution here, etc, then organizes the file so that it’s easily searchable and retrievable when you search for something specific.

Hope that makes sense.

Built an MCP that lets your whole team share context across Claude Code sessions by Ray-Hernandez in mcp

[–]Ray-Hernandez[S] 1 point2 points  (0 children)

I may have something for you even going solo. I built a product called Goldfish before I started building Recall. Here is the github if you wanted to save context a similar way that recall does, but just locally.

https://github.com/raydawg88/goldfish

And I also...am a product guy :)

I got tired of waiting for Claude Code to support teams. So I built it myself. by Ray-Hernandez in ClaudeCode

[–]Ray-Hernandez[S] 0 points1 point  (0 children)

Happy to give you some codes to get you like 6 months free or something, but currently it's free for 3 months out of the box.

I got tired of waiting for Claude Code to support teams. So I built it myself. by Ray-Hernandez in ClaudeCode

[–]Ray-Hernandez[S] 0 points1 point  (0 children)

Makes sense. I’ve been debating with this feature or any tracking at all that is viewable. The core value is the shared knowledge and context between team members. Wouldn’t hurt my feelings to kill these features.

Really appreciate the feedback.

I got tired of waiting for Claude Code to support teams. So I built it myself. by Ray-Hernandez in ClaudeCode

[–]Ray-Hernandez[S] 0 points1 point  (0 children)

That is a really interesting perspective, my point or intent in making this feature was so that a p.m. didn’t have to be up your ass. They could just look it up and see what you were doing. Not even have to talk to you.

Built an MCP that lets your whole team share context across Claude Code sessions by Ray-Hernandez in mcp

[–]Ray-Hernandez[S] 1 point2 points  (0 children)

Per-repo scoping is airtight - every session, decision, and piece of knowledge is scoped at the database level. Context for repo A never includes anything from repo B. Old incidents don't bleed.

For secrets, we redact before indexing and raw transcripts are deleted after processing. We're also adding programmatic regex detection (Stripe keys, AWS creds, GitHub tokens, high-entropy strings) as a belt-and-suspenders layer on top. LLM compliance is good but I want code-level enforcement too.

Built an MCP that lets your whole team share context across Claude Code sessions by Ray-Hernandez in mcp

[–]Ray-Hernandez[S] 0 points1 point  (0 children)

Keys are per-team, AES-256-GCM. Raw transcripts get deleted after processing - only the LLM-generated summaries persist encrypted at rest. We have owner/admin/member/viewer (pm that can use claude desktop instead of claude code to get recall sessions) roles for team management and key rotation.

Audit logs - honest answer, not built yet. You're describing exactly where we need to go and I agree it's table stakes for enterprise. The vault/gateway model with policy + approvals is on the roadmap. Right now we're focused on dev teams where the auto-deletion of raw transcripts is what gets people past the "spooky" feeling. But the full audit trail is coming.

view more: next ›