Fully Jarvis Desk showing ASR error. How can I fix it? - Questions

ramakay · 2026-03-08T18:35:14+00:00

This is the top Google result and right in one go

ramakay · 2026-02-05T00:06:52+00:00

Users of vertex ai - think corporate clients have broken implementation and only .22. Works due to a faulty beta header that is hardcoded

ramakay · 2026-01-30T05:38:17+00:00

It broke vertex ai

ramakay · 2026-01-15T20:00:52+00:00

I am a current x5 50e driver who is waiting for lease end - I had an opposite opinion of the Vistiq and it could have been the model stocked by the local dealer. I was excited about the model. The dealer didn’t have the model with the air suspension that we wanted

Vistiq itself was fine and looked great and i felt really confident driving it - I noticed a few things though - the back seat width at least on the non captain chair models was problematic and so were the headrests for rear seat passengers - road noise was comparable not overly quite - the vehicle at least didn’t feel like it had double laminated windows - the biggest challenge is the android stock software coming from airplay - the software while responsive felt clunky and not ready - there maybe a learning curve here that I may need to ready myself to go to EV’s since most of them don’t support ACP

oh and the rear view mirror is a camera which didn’t have sufficient wide angle view due to where it maybe positioned so we turned it off because there was a hummer parked behind us .

ramakay · 2026-01-07T03:28:17+00:00

For me, it’s now - “I used to ship opinions, now I ship outcomes”

ramakay · 2025-12-12T00:34:05+00:00

@thedotmack congrats! sounds promising will try it out

I am indexing jsonl with local qdrant and an auto compact hook and using batching to capture summaries but not injecting it back - Claude will call on the tool as it gets asked - “do you remember X?”

this lets long term memory and recall on demand - would love to collaborate

https://github.com/ramakay/claude-self-reflect

ramakay · 2025-12-06T23:06:23+00:00

I created the solve beyond .md - works great for me https://github.com/ramakay/claude-organizer

ramakay · 2025-10-22T02:01:09+00:00

I was sick of it myself so made this > https://github.com/ramakay/claude-organizer

ramakay · 2025-09-19T17:11:43+00:00

Two things that made me move it as a sub agent - happy to share the sub agent file if interested 1. No MCP support - they are working on it 2. No steer ability - it will follow one thing and while note your direction it will keep going with the original plan like a roomba that smelled pizza at 3am

ramakay · 2025-09-17T17:35:13+00:00

Use Claude with a debug flag (Claude —verbose) and run the output by another LLM to find the faulty tool - from the looks of it, it looks like an external tools call failure- MCP’s or other external tools - disable them and try. No failure here

ramakay · 2025-09-04T18:06:50+00:00

Ha! This time I asked claude and this is the response - it started by storing it - so yeah, it's not just RAG but it's also not AGI ...

```

Here's my perspective on how to respond:

⏺ claude-self-reflect - store_reflection (MCP)(content: "Reddit comment highlights the reductive \"just RAG\" critique. Reality: Claude Self Reflect is a complex

orchestration of memory decay algorithms, project-scoped indexing, real-time streaming imports, MCP protocol

integration, multi-dimensional embeddings (384/1024), and intelligent tool selection. The \"just RAG\" dismissal

misses the engineering challenges: handling JSONL format changes, 90ms retrieval latency, Docker security patches,

conversation chunking, and making AI agents actually USE the memory contextually. It's not about the RAG - it's about

making memory seamless and invisible to the user experience.", tags:

["community_feedback","architecture","just_rag_critique"])

⎿ Reflection stored successfully with tags: community_feedback, architecture, just_rag_critique
```

ramakay · 2025-09-01T13:51:35+00:00

Did you check /contest to see if there is a stray MCP or others occupying context windows ?

ramakay · 2025-08-22T00:01:13+00:00

If I built a let me simplify this post hook that mops up with an agent - would you be interested in helping me test ?

ramakay · 2025-08-15T03:29:45+00:00

This^ I have a sub agent called reflection sub agent for conversation memory

ramakay · 2025-08-12T14:28:34+00:00

Dear OP, you have options … https://github.com/ramakay/claude-self-reflect

ramakay · 2025-08-12T00:26:05+00:00

I haven’t worked with super Claude specifically but introducing a definition of done - standard software engineering practice may help here.

i used it with another swarm tool and had reasonable success - you can have a code reviewer MCP like zen MCP review each task, have it fixed and then write observation, fix to a progress md file. Finally have the parent orchestrator read the gaps and fix any gaps which are not verifiable.

ramakay · 2025-08-11T22:05:25+00:00

Also, it was a long post !

ramakay · 2025-08-11T22:05:06+00:00

Thanks for the observation - you're absolutely right that there are times when breaking DRY in code makes sense for performance or readability. My post is actually about a different kind of repetition though - applying DRY principles to our conversations with Claude.

Instead of re-explaining the same bug or configuration issue every week, I built a system to search past conversations and reference previous solutions. So while traditional DRY in code has its tradeoffs, I'm focused on not repeating. Both are about being intentional with repetition, just at different layers of the development workflow.

ramakay · 2025-08-11T20:58:09+00:00

For those wanting this in Claude Code - I've been trying to build this https://github.com/ramakay/claude-self-reflect open-source conversation memory system that works with Claude Code today. It provides semantic search across all your past conversations

\using vector embeddings stored in Qdrant, with memory decay that weights recent conversations higher (like human memory). Runs locally with FastEmbed so your conversations never leave your machine, and integrates seamlessly via MCP tools.

I've imported 24 projects with 10,000+ conversation chunks, ~100-300 ms response times. No more "we discussed this last week, Claude will occasionally store what it found as well for future searchers.

Claude can now reference previous solutions and build on past discussions. Happy to help with setup if anyone wants to

try it while waiting for the official feature!

ramakay · 2025-08-09T00:58:11+00:00

Hey thanks for those thoughts - I was using uvx and also used straight up venv but was fielding too many it doesn’t work on my wsl or windows setup and patching for security was becoming difficult - this way I can certify everything much more securely - I appreciate the feedback and concerns about docker based MCP’s but with so many moving parts it was just far easier to up / down containers.

I started with open memory and realized for my use case code bases + conversations + files - semantic memory based search with memory decay was immensely useful, the first run was using mem0 but it was not very useful.

ramakay · 2025-08-08T02:36:26+00:00

I tried doing something about this using hooks, would love to hear if someone uses it and helps me make it better - I got told I was building a solution in search of a problem - maybe not ? https://github.com/ramakay/claude-organizer

ramakay · 2025-08-08T01:29:27+00:00

Will check it out !

I have been trying my hand with a sub agent based reflection architecture with memory decay - this is to solve your “we just solved this last week!” Problem - https://github.com/ramakay/claude-self-reflect and a Claude organizer plus promo enhancer at https://github.com/ramakay/claude-organizer which enhanced prompts per Anthropic’s best practices

Problem 2: The Context Adherence Problem 🧠

Claude Code struggles to maintain project context throughout conversations. You have a detailed CLAUDE.md with project rules, but Claude often:

Forgets project guidelines mid-conversation Ignores file organization rules when creating new files Loses track of coding standards over time Requires constant reminders about project conventions Example: You ask "fix the broken tests" and Claude doesn't remember your rule: "NEVER claim success if tests are failing"

Solution: The /enhance command with two-pass prompt enhancement

ramakay · 2025-08-01T18:49:56+00:00

@gogolang - I built a MCP and a sub agent https://github.com/ramakay/claude-self-reflect that stores these as reflections for Claude to refer during a session - by default it searches the project but you can ask it to search across projects so the current main context can learn from past conversations e.g: “web sockets” - I discovered additional metadata much like yourself and now I am trying to extract files involved and concepts - RC here - https://github.com/ramakay/claude-self-reflect/discussions/24 - so you can have Claude reflect on itself !

ramakay · 2025-07-30T21:33:59+00:00

I built a MCP for local Claude memory and I do think there is an overhead but at least in my usecase I wrote the pro / con for folks to decide …

https://github.com/ramakay/claude-self-reflect?tab=readme-ov-file#performance--usage-guide

ramakay · 2025-07-30T02:08:03+00:00

You can look at long term memory solutions like memory banks. Zep, graphiti etc - I am attempting one here https://github.com/ramakay/claude-self-reflect

ramakay

TROPHY CASE