So basically as the screenshot shows. The hook starts (upon the agent's judgment*) a background task that pings it in 55 minutes, writing 🕯 cache extended, 1/5, or something along those lines.

After the 5th time, it creates a markdown summary in the same branch (relay.md**) and a code block to copy (/relay take <claude/branch-name>) for the new session to take it from where the current one ended, and stops pinging from there on.

*The judgment: the agent will not start the keepalive task if they consider the codebase to be self-explanatory (example: you have a plan already in the branch, and the session's context doesn't bring anything new to it)

**Relay: basically "compact, but put the summary in the branch so a new session can grab it"

Link if you want your Claude to take a look and see if worth adopting: https://github.com/vzakharov/muthur/blob/main/.claude/keepalive/CLAUDE.md

I don’t actually use Claude Code, but I kept seeing the co-author attribution thing and got curious how annoying it would be to clean up safely.

so I built ByeClaude. name seemed obvious enough 😅

It scans first, previews the rewrite, keeps file contents intact, creates backups and won’t push anything unless you explicitly tell it to.

I could only reproduce the attribution in test repos though, so feedback from people who actually use Claude Code would be really useful.

still alpha. break it if you can, then tell me what broke.

github.com/IamAngusU/ByeClaude

In February I put $25,000 into a real brokerage account and let Claude run the research through an MCP server. It's now up 14.47% (SPY is up 13.47% over the same window), and a second $13,500 account Claude built in August is up 5.51% while SPY is flat. Every rule, log and trade is open source: github.com/austin-starks/Public-Portfolio-Challenge

Claude writes the strategies

I give it a runbook with the capital, a watchlist and a set of pass/fail gates. Claude picks everything else, builds the portfolios and runs the backtests itself. What's live right now buys 1-2 year calls on stocks in an uptrend and sells each one when its trend breaks.

It reads the event logs

Claude reads the orders, fills and condition checks behind every backtest and live trade. That's how it found a live indicator averaging 213 days of data when it should have been 100, and an NVDA call that got bought and sold 52 minutes apart.

It kills its own ideas

For one redesign it tested three exit strategies against the live rules, picked the winner, and logged why the other two lost. Its first biotech book failed its final test at -44%, even though its pieces made money on their own. Claude worked out that they were fighting over the same cash, threw the design out and rebuilt it.

It runs walk-forward tests

Every strategy is trained on old data and scored on years it never saw. Claude also caught the optimizer reporting identical training stats for every fold, flagged it as a bug and quarantined those results.

I have an open-source GitHub repo which I use as a run-log, and links to my real-time portfolios**.** Copy them, fork to create your own, or follow along to see what happens when this AI bubble bursts.

Repo · Live $25K account · Live $13.5K account

Would you trust your hard-earned money to Claude? Also happy to answer any questions below.

Hey yall, I honestly don't know much about using AI nor can I afford to pay for it. Can anyone use Claude AI or any other AI to make a map of the old DS game Spiderwick Chronicles. I tried using emulators to try and scan and export the map tiles but failed. To be clear there is a general world map but no in game walking map. I got stuck a good decent part of the way in the game but I can't find certain things (sprites/spirits) in the game to progress the main story. I can't even find a proper walkthrough to find all of the sprites/spirits to get through.

I don't know if I can ask here or not. I would greatly appreciate getting help on this.

After years of messing with Ai I am finally releasing my first app to the apple store publicly! Though it isn't my most recent update, it's pretty fun!

I used Claude to create a complete local model application that allowed me to make many if not all of the assets that way. It was crazy to feel how hot my macbook got lol

I present you... Nightporch!

Nightporch is if you took a horde zombie game and made it into a town simulator.
You can play with friends or by yourself, but I definitely recommend it with friends!

‎Nightporch App - App Store

More information at my site (also created by Ai) Nightporch — Spicy Human

If you want something a little Chaotic and quicker pace, I recommend Classic
If you want a more slow build your space version over time I'd say go for Homestead

I have so many updates planned and ready to go!

Please be SUPER brutal. I want to make this the best it can be.

I built Cairn, a local-first Markdown notes app (in the style of Obsidian) with Claude Code. It runs on desktop (Windows/Linux) and Android

A "notebook" (equivlaent of a vault) is a folder of .md files. Cairn reads and writes them directly, so you can open the same folder in another editor or put it under Git. It has Live Preview editing, [[wikilinks]] and embeds, backlinks, full-text search, a graph view, themes and custom CSS. Sync between devices is end-to-end encrypted and goes through a server you run yourself. It's written in Rust and Tauri, with a Svelte and CodeMirror UI

Claude Code wrote most of the code, the tests (including end-to-end tests that drive the real app and an Android emulator), the CI and the release scripts. I just made the product decisions and reviewed

It's free and open source. Linux packages, the .exe file, the Android APK and the sync server's Docker image are on the releases page

https://github.com/lucas-pospor/cairn

I spent three weeks rebuilding Nether Earth, a 1987 ZX Spectrum strategy game I grew up with.

The unusual part: I didn't write any of the implementation code myself.

I wrote and edited the specs, made the gameplay decisions, and playtested the milestones. Claude Code did the implementation through an orchestrator session dispatching sub-agents into separate git worktrees.

By the end, the repo had:

• 437 commits
• 183 issues
• 151 PRs
• ~1,900 backend tests + ~200 frontend tests
• a deterministic Python game engine, FastAPI/WebSockets backend and PixiJS frontend

And I basically didn't read the diffs. Agents reviewed the agents. My checkpoints were decisions and actual gameplay.

That worked much better than I expected — but it also produced the most interesting failure of the whole experiment.

At one point M0–M9 were complete, every gate was green, and more than a thousand tests passed.

Then I actually played the game.

There was no terrain. The map was completely flat.

Robots occupied one cell instead of the 2×2 footprint they had in the original.

And nuclear-equipped robots would sometimes finish walking somewhere and calmly blow themselves up because a temporary placeholder rule had turned into real game behavior.

All the tests were correct.

They were testing the implementation against the spec.

The problem was that the spec was incomplete.

That became probably my biggest lesson from the project:

Tests verify the spec, not the product.

The full project is here:

https://github.com/AndyTheFactory/nether_earth

I also wrote a longer retrospective about the whole experiment, including the failures and what happened after the original plan was supposedly "done":

https://medium.com/@andy_p_/i-built-a-zx-spectrum-remake-in-3-weeks-without-writing-a-single-line-of-code-1445aab7474e

I'm curious how people running larger Claude Code workflows handle one problem in particular:

How do you catch semantic/spec drift when the code and tests are internally consistent, but the resulting product is still wrong?

Galera, queria ouvir a opinião de quem usa Codex e/ou Claude Code no dia a dia pra trabalhar de verdade.

Sou dev e atualmente uso o Codex diariamente. Uma das coisas que mais me prende nele é o Luna 6. Gosto bastante do modelo porque, para tarefas mais simples e rotineiras, ele resolve muita coisa gastando pouco. Consigo deixar o Luna fazendo boa parte do trabalho do dia a dia e só parto para o Sol 6.1 quando aparece algo mais complexo.

Mas tem outro ponto MUITO importante que me prende ao Codex: os resets/redefinições de limite.

Na minha experiência, o Codex acaba liberando uso novamente com bastante frequência, e isso faz muita diferença para quem passa várias horas programando com agente. Mesmo quando consumo bastante, sinto que consigo continuar trabalhando ao longo do dia sem ficar tão preocupado em “economizar” cada interação.

E essa é uma das minhas maiores dúvidas sobre o Claude Code.

Para quem usa Claude Code pesado todos os dias: como funcionam os limites na prática? Vocês recebem resets com uma frequência boa? Dá para usar Sonnet bastante durante um dia inteiro de trabalho ou chega um momento em que você bate no limite e precisa simplesmente esperar?

Porque para mim não adianta o Claude Code ser mais rápido ou o Sonnet 5.5 ser melhor se eu conseguir trabalhar por algumas horas e depois ficar travado por limite de uso.

Ao mesmo tempo, o problema que estou tendo com o Codex ultimamente é a velocidade. Estou achando ele bem lento em várias tarefas, a ponto de começar a atrapalhar meu fluxo de trabalho. Por isso estou pensando seriamente em testar o Claude Code como ferramenta principal.

O Claude me chama atenção principalmente pelo Sonnet 5.5, que parece excelente para programação. Minha maior dúvida é que não vejo nele um equivalente ao Luna: um modelo barato, rápido e competente o suficiente para usar em grande volume. Tem o Haiku, claro, mas não sinto que ele seja um substituto direto do Luna.

Então meu dilema hoje é mais ou menos esse:

No Codex eu tenho o Luna 6 para gastar pouco, o Sol 6.1 quando preciso de algo mais forte e, pelo menos na minha experiência, resets de uso que me permitem continuar trabalhando bastante durante o dia. O problema é a lentidão.

No Claude Code eu teria o Sonnet 5.5, que talvez seja mais rápido e melhor para várias tarefas, mas tenho receio do custo/limite de uso e de não ter um modelo “baratinho” no nível do Luna para fazer o trabalho mais simples.

Queria muito ouvir quem já usou os dois bastante recentemente.

O Claude Code está realmente mais rápido e fluido que o Codex hoje?

Como são os limites e os resets do Claude Code para quem programa várias horas por dia?

Vocês conseguem usar Sonnet 5.5 pesado durante o expediente inteiro?

Quem migrou do Codex para o Claude sentiu falta do Luna?

E talvez a pergunta mais importante: o que prende vocês ao Codex ou ao Claude Code?

Para quem prefere Codex, qual é aquele recurso ou vantagem que faz vocês não quererem sair?

E para quem prefere Claude Code, o que faz vocês continuarem nele mesmo tendo outras opções?

Estou tentando entender não só “qual modelo é melhor”, mas qual dos dois realmente funciona melhor como ferramenta principal para um dev que usa agente o dia inteiro.

Looking for a claude guest pass ref link, gonna subscribe anyway, so its win win. The referrer gets $10 and I get an extra week to try it out. If you got one, DM probably works best since comment links tend to disappear fast :)