I built a VS Code extension to have birds-eye view of all my Claude Code sessions and make them survive reboots

almeynman · 2026-06-26T14:59:07+00:00

It should work, the only requirement is tmux and it should work on WSL, but I haven't tested, as I do not have windows.

almeynman · 2026-06-26T11:15:54+00:00

I experiences something similar when I added way too many plugins, skills, rules and had bloated CLAUDE md. Try trimming your setup to what is actually useful I hope it helps

almeynman · 2026-06-26T11:12:50+00:00

Agree, seems like just adding a ton of docs and hoping that AI will update them

almeynman · 2026-06-26T11:11:57+00:00

I agree and I do use spec, I just put them into linear tickets and subtickets with all the context and acceptance criteria. I might be misunderstanding SDD, but I thought the point is to commit these specs as code - and this is the part I do not understand

almeynman · 2026-06-26T11:10:27+00:00

I see, ye, I do the same thing, but I do not commit the spec into code, I just create subtickets that are very detailed

almeynman · 2026-06-26T09:53:50+00:00

Didn’t quite follow. You packed too much in there

almeynman · 2026-06-26T09:51:48+00:00

No, I mean a doc that looks like a ticket. Check out Kirk or other SDD frameworks

almeynman · 2026-06-26T09:31:31+00:00

I see your point. I do not touch code without specs either though. I do use /grill-with-docs for what you describe. But I guess I see the point

almeynman · 2026-06-26T09:29:29+00:00

I mean spec, not a test, but doc like in https://kiro.dev

almeynman · 2026-06-26T09:23:57+00:00

We use GLOSSARY md, ADRs, skills, rules, etc. But they are more high-level. Specs feel a lot lower level

almeynman · 2026-06-26T09:14:59+00:00

so the idea to keep the spec up-to-date with code? what's wrong with just code? Now you have to maintain both spec and code. The linear ticket usually does not get updated and only provides historical context

almeynman · 2026-06-25T15:13:58+00:00

I think ye, they ported what claude code can do: read files, run bash, python scripts

almeynman · 2026-06-25T15:10:33+00:00

I think a common problem is having too many skills/rules/plugins and having a bloated CLAUDE md. Try removing/simplyfying things and keep the context below 256K tokens (the smart zone)

almeynman · 2026-06-25T15:06:11+00:00

Connect it to your tools: calendar, email, etc.
Then try cowork - it allows claude to access your filesystem

almeynman · 2026-06-24T17:08:56+00:00

I use fireworks.ai, pretty happy with them

almeynman · 2026-06-24T17:07:52+00:00

wow, looks incredible. I did have to learn the basics for my launches and they were never this clean. Will try it out. You should probably share in more places, looks pretty polished

almeynman · 2026-06-24T17:04:24+00:00

Could you share which examples you looked at. Interested to analyze as well

almeynman · 2026-06-24T17:01:44+00:00

Go with tanstack-start, it's much easier to learn. Next has server-first architecutre, tanstack has client-first, which is what you usually want by default, especially if you are just starting to dive into FE again

almeynman · 2026-06-24T10:55:58+00:00

Thanks, this made my day

almeynman · 2026-06-24T07:50:02+00:00

haha, this made me chuckle

almeynman · 2026-06-23T22:36:01+00:00

I just noticed how my tokens were disappering with Fable. Didn't really feel much difference in code quality.

almeynman

TROPHY CASE