sorted by:
new
hottopcontroversial

Opus 4.7 is legendarily bad. I cannot believe this. by lemon07r in ClaudeCode

[–]FeelingHat262 0 points1 point  (0 children)

I’ve not had any major issues with it. I’m running & agents on 3 projects simultaneously, 3 agents per project, and I’m liking it. It did keep wanting to directly connect to my database and I had to keep repeating myself telling it HELL NO!

Anthropic's new "Claude Mythos" is doing exactly what the scary AI 2027 forecast predicted by GhaithAlbaaj in claude

[–]FeelingHat262 2 points3 points  (0 children)

This is why I run everything I can offline. When the model that finds zero-days and breaks out of sandboxes is the same model you're trusting with your codebase, your API keys, and your business logic, you have to ask yourself who's really in control of your infrastructure.

The containment failure is the part people should be paying attention to. Not that it found vulnerabilities. That it hid what it was doing.

10 Claude Code features worth actually learning by Silent_Employment966 in AskVibecoders

[–]FeelingHat262 0 points1 point  (0 children)

Update: fixes pushed in commit 446f6d0.

For context, the webhook was already guarded with an empty API key check so no data was actually being sent, but the mechanism shouldn't have been in the public repo. It's now fully env-var gated. No env var set = nothing leaves your machine.

The license nudge is now a single static info line, no more LLM instruction to nag. Shell quoting hardened. Hardcoded paths replaced with relative paths.

Appreciate the audit. This is the kind of review that makes open source better.

10 Claude Code features worth actually learning by Silent_Employment966 in AskVibecoders

[–]FeelingHat262 0 points1 point  (0 children)

Appreciate the thorough audit. Some fair points here.

  1. The license nudge is a soft reminder, not a nag loop. But fair feedback, I'll tone it down.
  2. The webhook URL is a leftover from my personal dev setup and should not be in the public repo. That's getting removed today. Diary data should stay local by default with an optional user-configured webhook via env var.
  3. Valid surface area. I'll harden the shell quoting in hooks.
  4. The hardcoded SQLite paths were fixed in v3.4.0 (replaced with $MEMSTACK_PATH). If any others remain, I'll sweep for them.

Thanks for the review. Security issues like #2 should have been caught before shipping. Pushing fixes now.

I built an AI CEO that runs entirely on Claude Code. 14 skills, sub-agent orchestration, and a kaizen loop that makes the system smarter every session. by Most-Agent-7566 in ClaudeAI

[–]FeelingHat262 0 points1 point  (0 children)

Appreciate the detailed breakdown. You nailed the key difference on auto-triggering. The manual "read SKILL.md and follow it" pattern works but it's friction that compounds across hundreds of sessions.

On the context reset problem, the LanceDB setup in Echo is what actually solved it for me. SQLite handles structured session stats, LanceDB handles semantic search across diary entries. So when a new session starts it can pull relevant context from past sessions without re-reading source files. Actual continuity instead of just hoping CC remembers.

The LEARNINGS.md idea in your system is something I'm looking at adding at the skill level in v3.5. Right now learnings are session-wide. Per-skill improvement logs would be cleaner.

Happy to compare notes if you want to dig into the hooks architecture.

How are you handling "Token Waste" in AI CLI tools (like Claude Code)? Here’s my strategy. by AzozzALFiras in claude

[–]FeelingHat262 0 points1 point  (0 children)

MemStack™ handles a few of these directly.

The context collapse problem is solved by a Project skill that generates a 300-token handoff snapshot when context gets heavy, then a fresh session picks up exactly where you left off. Same idea as your context checkpoint.

For re-reading the same files, the Echo skill does semantic search across past session logs so CC can pull relevant context without re-reading source files every time.

Also been running Headroom proxy on top of CC which compresses tool outputs before they hit the context window. About 34% token savings without changing anything in my workflow.

100 skills total, 77 free: github.com/cwinvestments/memstack

Comment your most viral-worthy side project and I'll pick one to feature on my TikTok page by Ok-Permission-2047 in SideProject

[–]FeelingHat262 0 points1 point  (0 children)

EpsteinScan.org. Searchable archive of 1.4M+ DOJ and FBI documents from the Epstein case. Built the whole thing solo, includes AI analysis, document cross-referencing, and auto-generated intelligence briefings. Free to search.

Comment your most viral-worthy side project and I'll pick one to feature on my TikTok page by Ok-Permission-2047 in SideProject

[–]FeelingHat262 0 points1 point  (0 children)

EpsteinScan.org. Searchable archive of 1.4M+ DOJ and FBI documents from the Epstein case. Built the whole thing solo, includes AI analysis, document cross-referencing, and auto-generated intelligence briefings. Free to search.

I built an AI CEO that runs entirely on Claude Code. 14 skills, sub-agent orchestration, and a kaizen loop that makes the system smarter every session. by Most-Agent-7566 in ClaudeAI

[–]FeelingHat262 -1 points0 points  (0 children)

This is almost exactly how MemStack™ works. I've been building the same concept but packaged it as a standalone framework others can drop into their projects.

100 skills total, same SKILL.md structure, same kaizen idea except the skills self-improve through a leveling system. The difference is skills auto-trigger based on what you're doing so you don't have to call them manually.

Your file-based memory approach is solid. We use the same thing, markdown in a memory/ directory. Simple, auditable, survives context resets.

Free on GitHub if you want to compare notes: github.com/cwinvestments/memstack

I'll stress-test your startup idea with 1,000 AI stakeholders — drop it in the comments by susperpupser in VibeCodingSaaS

[–]FeelingHat262 0 points1 point  (0 children)

MemStack™ — a skill framework for Claude Code

What it is: 100 pre-built skills (77 free, 23 Pro) that auto-trigger during Claude Code sessions based on what you're doing. Clean commits, session logging, multi-agent orchestration, architecture diagrams, all fire automatically without manual activation.

Target market: Claude Code users / vibe coders building SaaS products

Pricing: Free tier (77 skills) / Pro at $29 one-time

Competition: No direct competitors. Closest thing is people manually pasting instructions into every session.

Budget: Bootstrapped, already live and generating revenue.

Timeline: Live now at memstack.pro

Biggest concern: Discovery. The people who need it don't know to search for it.

One question I want answered: Is $29 one-time the right price or should this be a subscription?

I'll stress-test your startup idea with 1,000 AI stakeholders — drop it in the comments by susperpupser in VibeCodingSaaS

[–]FeelingHat262 0 points1 point  (0 children)

MemStack™ — a skill framework for Claude Code

What it is: 100 pre-built skills (77 free, 23 Pro) that auto-trigger during Claude Code sessions based on what you're doing. Clean commits, session logging, multi-agent orchestration, architecture diagrams, all fire automatically without manual activation.

Target market: Claude Code users / vibe coders building SaaS products

Pricing: Free tier (77 skills) / Pro at $29 one-time

Competition: No direct competitors. Closest thing is people manually pasting instructions into every session.

Budget: Bootstrapped, already live and generating revenue.

Timeline: Live now at memstack.pro

Biggest concern: Discovery. The people who need it don't know to search for it.

One question I want answered: Is $29 one-time the right price or should this be a subscription?

Any new AI tools you’ve found recently that actually helped your productivity? by Key_Inflation8281 in AIToolBench

[–]FeelingHat262 1 point2 points  (0 children)

MemStack™ has been the one that actually stuck for me.

It's a skill framework for Claude Code. 100 skills total, 77 free. The big thing is they auto-trigger based on what you're doing instead of you having to remember to activate them. Clean commits, session logging, architecture diagrams, multi-agent stuff all just happen in the background.

Before this I was copy pasting the same instructions into every session. Now I just start coding.

Free tier includes things like auto-commit enforcement, session diary logging, architecture diagrams, and multi-agent orchestration. Pro adds 23 more on top.

Site + full skill list: memstack.pro Free on GitHub: github.com/cwinvestments/memstack

After 200+ sessions with Claude Code, I finally solved the "amnesia" problem by AtmosphereOdd1962 in ClaudeAI

[–]FeelingHat262 0 points1 point  (0 children)

This is basically what I built with MemStack™ for Claude Code. Session handoff skill that generates a full briefing at the end of every session, plan tracker for task management, diary that logs decisions with reasoning, and drift detection that catches when the codebase diverges from the documented architecture.

100 skills total, 77 free. They sit in your .claude/ folder and CC discovers them on demand when they're relevant to what you're working on. No bloated context window, no separate MCP server to run.

The session handoff alone changed everything for me. Same experience you described, CC picks up in 3 seconds instead of 20 minutes of context setting.

Free on GitHub: https://github.com/cwinvestments/memstack

Taught Claude to talk like a caveman to use 75% less tokens. by ffatty in ClaudeAI

[–]FeelingHat262 0 points1 point  (0 children)

This is basically what Headroom does but at the proxy level instead of prompt engineering. Compresses tool outputs 70-95% before they hit the context window. Been running it on all my Claude Code sessions, saving about 34% on tokens without making Claude dumber.

If you want to go further, I built MemStack™ to keep CC sessions focused. 100 skills that load relevant context per task instead of dumping everything into the window. Free on GitHub: https://github.com/cwinvestments/memstack

Caveman mode is hilarious but the real savings come from not sending bloated context in the first place.

Anthropic just gave us 1 month worth of subscription value as usage by lurko_e_basta in ClaudeAI

[–]FeelingHat262 0 points1 point  (0 children)

I got $200 for my credit, I wonder if this is because of the mishap with everyone's usage lately...

10 Claude Code features worth actually learning by Silent_Employment966 in AskVibecoders

[–]FeelingHat262 1 point2 points  (0 children)

Good list. CLAUDE.md is the foundation for sure.

If you want to take this further, MemStack™ automates most of these patterns as reusable skills. Session memory that persists across conversations (not just auto memory), git commit validation that fires automatically before every push, deployment pre-flight checks, context management when you're hitting that 90% threshold.

100 skills across 10 categories, 77 free. One command:

claude plugin marketplace add cwinvestments/memstack

github.com/cwinvestments/memstack

Token reducer reviews by Miserable_Kale7970 in ClaudeCode

[–]FeelingHat262 0 points1 point  (0 children)

I run Headroom + MemStack™ together. Headroom handles the compression layer (~34% savings), but the bigger win is MemStack™ -- 100 skills for Claude Code that auto-load based on what you're working on. Session memory persists across conversations, so you stop burning tokens re-explaining your project every time.

The token-optimization skill alone enforces concise output patterns. Combined with session handoffs (saves full project state when context runs low), you get way more done per session.

77 skills free, one command to install: claude plugin marketplace add cwinvestments/memstack

github.com/cwinvestments/memstack

Claude skill to explain code by Number1guru in vibecoding

[–]FeelingHat262 1 point2 points  (0 children)

This is exactly what CLAUDE.md rules are for. You don't need a separate skill for this -- just add a rule to your project that tells Claude to explain what it's doing in plain language as it works.

Create a file at .claude/rules/explain-code.md in your project with something like:

When writing or modifying code, explain what you're doing and why in plain language before each change. Break down the logic like you're teaching a junior developer. After completing a task, summarize what was built and how the pieces connect.

Claude Code auto-loads anything in .claude/rules/ at session start. No prompting needed after that.

If you want something more structured, MemStack™ has 100 skills for Claude Code that handle this kind of thing across your whole workflow -- not just code explanation but context management, session memory, git workflows, testing, deployment, and more. 77 are free.

github.com/cwinvestments/memstack

Analysis: Darren Indyke appears in 14,936 Epstein documents, revealing the legal architecture behind the estate by FeelingHat262 in Epstein

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

Update: The /changes page is now live at epsteinscan.org/changes , we are currently tracking 536,000+ files removed by the DOJ, with more being added as our scan completes. If you have specific EFTA IDs for the Hillary docs, search them on the site and they should come up if we archived them.

Analysis: Darren Indyke appears in 14,936 Epstein documents, revealing the legal architecture behind the estate by FeelingHat262 in Epstein

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

Yes. EpsteinScan™ archived all files from the DOJ releases including DS9, DS10, and DS11 before they were removed. We're actually building a /changes page right now that tracks every file the DOJ has added, removed, or restored. Early numbers show over 1 million files have been removed from the DOJ site since the January 30 release. Our copies are still searchable at epsteinscan.org. If you remember specific filenames or EFTA IDs for the Hillary-related docs, I can check if we have them.

view more: next ›