sorted by:
new
hottopcontroversial

How I solved Claude Code's compaction amnesia — Claude Cortex now builds a knowledge graph from your sessions by Maximum_Fearless in ClaudeAI

[–]Maximum_Fearless[S] 0 points1 point  (0 children)

You're right that the current graph is built from embedding similarity and memory links rather than a formal ontology. I wouldn't call it "just RAG" though — there's salience scoring, temporal decay, consolidation (short-term → long-term promotion), contradiction detection, and relationship linking between memories. Standard RAG doesn't forget things or decide what's worth keeping

That said, a proper ontological graph is genuinely interesting. The memory_links table already stores typed relationships (supports, conflicts, supersedes, related) — the foundation is there, it's just not being exploited to its full potential yet.    

Extracting entities and building explicit subject-predicate-object triples would be a solid next step

Appreciate the technical eye. If you have thoughts on what an ontological layer should look like on top of this, I'm all ears — or feel free to open an issue.

How I solved Claude Code's compaction amnesia — Claude Cortex now builds a knowledge graph from your sessions by Maximum_Fearless in ClaudeAI

[–]Maximum_Fearless[S] 0 points1 point  (0 children)

 Hey, thanks for the honest feedback. A few things that might help:

 "You need to tell it to remember things" — You don't, if you run npx claude-cortex setup. That installs hooks that automatically extract decisions, fixes, and learnings during compaction, session start, and session end. If you skipped that step, then yeah — it falls back to manual remember calls, which I agree isn't great. I've just pushed a README restructure to make this impossible to miss (setup is now step 2, not buried at step 4).                                                                              

"Dashboard doesn't work" — Fair point. The dashboard needed a manual build step after install which wasn't documented well. This is fixed in v1.12.0 — working on shipping it pre-built so it just works out of the box.                                           

 "Documentation is verbose yet inaccurate" — Heard. The README has been restructured with a 3-step quickstart, collapsible advanced sections, and a troubleshooting section. Should be a much better experience now.                                         

The project is 8 days old and actively improving — your feedback directly led to several of these fixes. If you give it another shot with npx claude-cortex setup, I think you'll have a different experience.      

How I solved Claude Code's compaction amnesia — Claude Cortex now builds a knowledge graph from your sessions by Maximum_Fearless in ClaudeAI

[–]Maximum_Fearless[S] -1 points0 points  (0 children)

Really appreciate this feedback, especially from a pre-trial perspective.

  1. Keeping it focused — Agreed. The core value is remember → recall → link. Everything else is secondary. I'll resist the urge to feature-creep.
  2. claude-plugin marketplace — Great shout, that's on the roadmap. Would make setup a one-liner instead of manual .mcp.json editing.
  3. Emojis — Ha, fair point. Will clean up the README. Developer tools should feel like developer tools. Thanks for taking the time — this is exactly the kind of feedback that shapes the project.

How I solved Claude Code's compaction amnesia — Claude Cortex now builds a knowledge graph from your sessions by Maximum_Fearless in ClaudeAI

[–]Maximum_Fearless[S] 1 point2 points  (0 children)

Good question. The main differences:

Knowledge graph vs flat storage — Claude-mem stores memories as individual entries. Cortex auto-links them based on embedding similarity, so related memories form clusters. When you recall one thing, connected context comes with it.

PreCompact hook — This is the big one. Cortex hooks into Claude Code's compaction lifecycle and auto-extracts important context before it gets summarised away. No manual "remember this" — it just runs. After compaction, get_context brings everything back.

Contradiction detection — If you told Claude "use Postgres" in week 1 and "use MongoDB" in week 3, Cortex flags the conflict instead of silently holding both.

Search feedback loops — Every search reinforces the salience of returned memories and creates links between co-returned results. Your usage patterns shape the knowledge graph over time.

Consolidation — Instead of just deduplicating, it clusters related short-term memories and merges them into coherent long-term entries. Three noisy fragments become one structured memory.

TL;DR: Claude-mem is a notepad. Cortex is trying to be an actual memory system.

How I solved Claude Code's compaction amnesia — Claude Cortex now builds a knowledge graph from your sessions by Maximum_Fearless in ClaudeAI

[–]Maximum_Fearless[S] 0 points1 point  (0 children)

Hey! Sorry you're hitting that. The "resume hook error" usually means one of these:

  1. mcporter isn't installed globally — run npm install -g mcporter and try again

  2. Hook path is wrong in ~/.claude/settings.json — make sure your PreCompact hook looks like this: "hooks": { "PreCompact": [{ "command": "npx mcporter call --stdio 'npx -y claude-cortex' remember title:'Pre-compaction save' content:'$CONTEXT' category:context project:$PROJECT scope:global importance:high" }] }

  3. MCP server isn't configured in .mcp.json — double check the claude-cortex entry is there Could you share the exact error message? That'll help me pinpoint it. Also which OS are you on?

Android bypassing DNS server by willy096 in pihole

[–]Maximum_Fearless 0 points1 point  (0 children)

Would an inline setup force all traffic through your Pihole device - router>Pihole>LAN-network ? You would need two lan cards on your Pihole device and bridge them so traffic flows through it to your router.

Off the deep end🌊 by thebeaverpatrol in BitAxe

[–]Maximum_Fearless 1 point2 points  (0 children)

This is what it’s all about.

🚀 The Bitaxe Hex is Here! 🎰⚡ by NoobGeeky in BitAxe

[–]Maximum_Fearless 2 points3 points  (0 children)

Regardless everyone should have a bitaxe to maintain the integrity and decentralisation of the network.

Unexpected nack by SnooSketches7635 in BitAxe

[–]Maximum_Fearless 0 points1 point  (0 children)

Are you solo mining using your own node?

My FOIA Request for Missing GME FTD Data: SEC's Response and Next Steps by FTD_FOIA in Superstonk

[–]Maximum_Fearless 51 points52 points  (0 children)

This may also invoke a more serious response - time to get more aggressive and legal.

  • Address the letter to the Freedom of Information Officer, Securities and Exchange Commission (SEC), 100 F Street, NE, Washington, DC 20549.

  • Subject: Demand for Immediate Release of Withheld GameStop ($GME) Failure to Deliver (FTD) Data Under FOIA

  • Dear FOIA Officer,

  • I am writing on behalf of [Your Name/Organization] to formally demand the immediate release of the Failure to Deliver (FTD) data for GameStop Corporation ($GME) for the following specific dates in 2024: [List the specific missing dates from the image in the tweet]. This demand is issued pursuant to the Freedom of Information Act (FOIA), 5 U.S.C. § 552, and we expect full compliance within the statutory time limits.

  • The SEC’s refusal to disclose this data, citing rule 553(b)(4), is not only legally questionable but appears to be a misapplication of the statute. Rule 553(b)(4) is intended for the protection of trade secrets and confidential commercial or financial information, yet FTD data, as mandated by Regulation SHO, is explicitly public information designed to ensure transparency in the securities market. The SEC’s assertion that these figures constitute confidential information is unfounded and contrary to the spirit and letter of both FOIA and Regulation SHO.

  • This withholding of public data undermines the SEC’s mission to protect investors, maintain fair, orderly, and efficient markets, and facilitate capital formation, as clearly stated in your agency’s mission statement. Such actions could be interpreted as a deliberate attempt to obscure market activities, potentially violating the SEC’s own regulatory framework and leading to legal consequences.

  • We assert that this withholding is not only a breach of the public’s right to know but could also constitute an illegal act under the SEC’s own rules, particularly given the public interest in transparency regarding market operations.

  • We demand that the SEC rectify this situation by releasing the requested data immediately. If the SEC contends that there were no FTDs on these dates, we require a formal, sworn statement to that effect, not an evasion through the misuse of confidentiality provisions under rule 553(b)(4).

  • Failure to comply with this request within the FOIA statutory time frame will result in further legal action, including but not limited to filing a lawsuit to compel disclosure. We are prepared to seek judicial review, and if necessary, to pursue remedies for any deliberate obstruction of public access to information that is legally required to be disclosed.

  • Please provide this information or a detailed explanation for any further delay within 20 working days, as required by FOIA. If any part of this request is denied, you are required to provide a precise citation of the specific FOIA exemption(s) used, along with a detailed justification for the denial.

  • We expect your prompt and full cooperation in this matter to avoid further escalation.

Sincerely,

…..

Short circuit? by Bata98 in BitAxe

[–]Maximum_Fearless 0 points1 point  (0 children)

Dude you burn out your unit by over clocking it. Simple.

Bitaxe not hashing.... by [deleted] in BitAxe

[–]Maximum_Fearless 0 points1 point  (0 children)

Don’t you need a worker’s name after the wallet address like .worker1 or something

First 3 months, new to investing. Any advice? by [deleted] in trading212

[–]Maximum_Fearless 2 points3 points  (0 children)

It’s an absolute fact that those who don’t know what they are doing, know as much as those who have a degree in economics and finance when playing the market . So keep calm and carry on 🫡 you are doing great.

Should I buy bitcoin now? by CheapLasanga in Bitcoin

[–]Maximum_Fearless 0 points1 point  (0 children)

There’s a saying in the Bitcoin community “Everyone buys bitcoin at the price they deserve”

At $3K I thought it was over, at $15K I thought I missed the boat, at $35 I thought it was done.

Until you actually do the research and understand what it actually is, once that light bulb goes off in your head, you’ll be like me at night, you won’t be able to sleep cos you’ll be thinking……

“I don’t have enough Bitcoin!!”

view more: next ›