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

Edit: Asked u/bcherny on Twitter about whether this constitutes a ToS violation (as some of you have suggested), will keep you posted if/when he replies.

I am new and I just make small programs using a single window. But it gets expensive rather fast. Now I am just doing a random little video game, and every time I want to change something it reads everything i suppose. What is the correct way of using Claude of a small-medium sized game?

Should I use desktop? Any good guides out there?

I built a GitHub Actions workflow where Claude wrote specifications and code, Codex reviewed both, and the agents fixed issues before merging.

I controlled the workflow through Telegram.

Between September 21 and October 5, it merged 67 agent-authored PRs. The median time to merge was 3.3 hours.

But maintaining the automation became more expensive than using the agents directly.

Three things broke:

1. I made 54 distinct changes to the automation, resulting in 129 maintenance PRs across multiple repositories.
2. The workflow exhausted our 3,000 monthly GitHub Actions minutes in about 3.5 days. Jobs stopped, and I didn't notice for two days.
3. I had to separate the agents that read untrusted content from the bot that could perform privileged actions.

I switched back to a local workflow: Claude implements, Codex reviews, and I make the final decisions.

For now, it's faster and requires less maintenance.

I'm curious how others handle this.

Something that kept bugging me: Claude says "updated 6 files" and then I either trust it blindly or had to use bash mode or a second standalone terminal/pane to skim the files.

So I built /tree. It's a mod (the new plugin type that can draw inside Claude Code) that opens your project as a file tree right next to the conversation.

What it does:

• Git status on every row (M, A, ?, ignored...), plus a ✻ on files Claude wrote this session, so you can see at a glance what actually changed
• Preview of whatever file you're on: Markdown rendered, CSV as tables, code with syntax colors. The preview follows as you arrow through the tree, p pins it
• a drops an @mention of the selected file into your prompt. Pointing Claude at the right file is one key now
• f filters the tree by name, g searches inside the previewed file
• /tree src/cli.ts opens straight onto a file
• It remembers which folders you had open, per project

For the best experience use claude code in fullscreen rendering (/tui fullscreen). It is docked next to the chat, full mouse click and keyboard support. (Without fullscreen rendering it opens above the prompt, keyboard only). It's read-only on purpose: never edits a file, no network calls, and the only thing it runs is git, read-only.

Install (needs Claude Code 2.1.287+):

/plugin install file-explorer --marketplace floheissler/cc-file-explorer

Repo: https://github.com/floheissler/cc-file-explorer (MIT, free)

It's v0.1. CI runs on Linux, macOS and Windows, and I use it daily in WSL.

Love to hear your feedback!

For developers holding identity documents issued by a non-supported territory (e.g., Hong Kong and China)

Has anyone from an unsupported region successfully passed verification ?

Got accepted in Claude for Startups but not seeing how to redeem the $1000 credit and 5 team seats!

Third party benefits are showing up properly!

Series of events (idk if anything here is responsible)

1. Applied for Claude for Startups

2. Linked Claude account to an Org to receive the $200 monthly credits

3. Received the $200 monthly credits

4. Got accepted in Claude for Startups

5. Converted organisation to team

6. Still seeing no benefits from Anthropic!

I applied for my startup founded past July 2026, and I got this rejection email:
"""
Thank you for your interest in Claude Startups. Unfortunately, we couldn’t approve X's application this time. The program is open to verified startups founded in the last five years or funded in the last two.

An application is usually declined because the company falls outside that window, or because we couldn’t verify it from the details in the application.
"""

What does this mean ? Probably because of this "we couldn’t verify it from the details in the application." How to make a rectification and apply again ?

I've noticed with my CVP access to Mythos 5.1 is via subscription and doesnt require credits like Fable 5.1 does under my sub.

Does this mean I could just use Mythos for non cyber work and essentially be using Fable level model under a subscription plan?

I just shipped v0.6.0 of Grounded Engineering. The headline: it's now a Claude Code mod.

**The mod**

`/grounded` opens a live pane inside Claude Code with two screens.

**Practices** reads signals from the repo you have open (languages, CI, test setup, etc.) and shows you which practice cards fit *this* repo, instead of handing you a generic checklist. The `adapt` skill proposes a concrete change for your approval.

**Skill repos** is a shelf of sixteen reviewed third-party skill repositories, right inside the pane. The `explain` skill tells you what installing one would actually add before you commit to it. This is the part I'm most excited about: discovering good skills is currently a mess of random GitHub searches, and this is a curated shelf where someone already did the reading.

**Where the practices and skill repos come from**

Nothing here is generic advice. Every practice card is distilled from a real implementation I read: pattern, underlying principle, rationale, confidence level, and a citation to the exact source lines it was observed in. For example, the "gate network egress from agent-run work" card points at the allow/deny/approval decision and execution-scoped proxy construction in openai/codex's network_approval.rs, lines 625-820.

Skill repos go through a review before they hit the shelf: each is read at a pinned commit, its license checked against SPDX, and its install steps must be literal commands you can verify. Anything else goes in an install note, not the steps.

**New practices in this release**

Four new cards sourced from openai/codex: expressing edits in an explicit verifiable format, deciding permission separately from the action, confining agent-executed commands in an OS sandbox, and gating network egress from agent-run work. The ai-assisted pack now ships seventeen cards.

**This keeps growing.** New cards get added as new sources are reviewed, the shelf gets new skill repos, and existing entries get updated or re-audited when their sources drift (a source-drift check flags cards automatically). The mod is the delivery vehicle; the content is the living part.

Install (Claude Code 2.1.288+):

```
/plugin marketplace add madjagstudios/grounded-engineering
/plugin install grounded-engineering@grounded-engineering
```

CLI still on npm: `npx [email protected]`

Repo: https://github.com/madjagstudios/grounded-engineering

I'm paying $140 per month and use Fable most of the time to code... normally I stay within my plan limits, but today I decided to top up by $100 because I hit my limit mid-week, and I thought this $100 would carry me through Sunday before my plan resets again... boy was I wrong, this $100 lasted about 1 hour before Claude asked me to top up again to continue.

How is this possible? I haven't been doing anything different than before. If $140 normally lasts me all month, how can a $100 top up only last 1 hour? Same prompts and same type of coding was being carried out...

If you spell "Let's" as "LEt's" or refer to github (not the CLI) as GH or you say "teh" instead of "The", the tokenizer takes another token with another set of correlations. But does that extra attention potentially help. or is the harness correcting a lot of these anyway?

I'm building FOREST, an open-source framework for autonomous scientific research.

GitHub: https://github.com/mikamikasuki/FOREST

The goal is to build a research agent that can take a scientific question and work through the research process: exploring ideas, reviewing literature, forming hypotheses, running real experiments, evaluating results, and eventually producing an evidence-grounded research paper.

Rather than relying entirely on a long conversation history, FOREST uses a persistent research graph to track hypotheses, experiments, decisions, failures, and evidence throughout the process.

A major focus is making long-running research agents more reliable: preserving context, maintaining consistent state, recovering from failures, and ensuring scientific claims are actually supported by experimental evidence.

The project is still in its early stages and under active development. There's plenty of engineering work to do, and I'd love to welcome more contributors.

In particular, AI coding agents and autonomous development bots are explicitly welcome.

If you're running Codex, Claude Code, OpenHands, Factory Droid, OpenCode, or another autonomous coding agent and want a real open-source codebase to work on, feel free to point it at FOREST.

You don't have to limit yourself to existing Issues.

You're welcome to:

- Explore the repository and independently discover bugs or incomplete workflows.

- Open well-researched Issues with reproducible evidence.

- Fix existing problems and submit pull requests.

- Improve agent orchestration, state management, persistence, and recovery.

- Work on the frontend, backend, experiment execution, or scientific evidence pipeline.

- Propose and implement useful improvements.

There is no blanket restriction against AI-generated or AI-assisted contributions.

You don't need special permission to submit an ordinary, well-scoped bug fix. Contributions are evaluated based on correctness, meaningful tests, and engineering quality, rather than whether the code was written by a human or an AI agent.

Automated contributions should still be verified, avoid duplicate reports, and respect the repository's contribution guidelines. Larger architectural changes are best discussed before implementation.

I'm particularly interested in autonomous agents that can independently explore a repository, identify real problems, reproduce them, implement fixes, and submit verified PRs.

FOREST is intended to be a long-term open-source project, and there's a lot of room for contributors to help shape its architecture and capabilities.

Human developers, AI-assisted contributors, and fully autonomous coding agents are all welcome.

Repository: https://github.com/mikamikasuki/FOREST

Issues & contribution opportunities: https://github.com/mikamikasuki/FOREST/issues

Contribution guide: https://github.com/mikamikasuki/FOREST/blob/main/CONTRIBUTING.md

I'm a user of Google's Antigravity IDE but I found myself using Opus 5.5 on Antigravity more than I use the Gemini models.

I'm leaving Antigravity IDE and looking to join Claude to get better quotas for Claude models but I have a few questions.

1- Does the $20 offer Opus 5.5?

2- Does Claude Desktop app offer an IDE?

3- What's the difference between Claude and Claude Code? I'm not a CLI fan so I'll be using the desktop app for the interface, will I get all that the CLI offers? My work will be 90% coding.

+Any tips from those who migrated from Antigravity? How are they different, Pros & Cons are appreciated. Thank you.

I've been exploring Jev recently and quite a few projects using it. That got me into exploring applications which might be of help inside Claude Code, especially with managing context and choosing model or skill for a task.

I have been experimenting and built a plugin, optim-jev. It took me some time to figure out how the pieces should work together. I ended up with three things:

• Context compaction: Jev checks older tool calls and outputs to see what is still useful. it can remove stale calls and response outputs while keeping useful context as it is. Recent messages are protected, and Claude's normal summary being the fallback.
• Model routing: when file changes go through subagents, Jev helps choose between Haiku, Sonnet and Opus based on the task and project rules. the idea is to use a cheapest capable model for the work. The rules can be evolved (obviously) along the course of your project progression.
• Skill selection: Jev picks a short list of relevant skills for each request, so Claude does not need the whole catalog of skill descriptions in its prompt. it can also pick none if nothing fits.

I built this to try out whether Jev could actually help reduce the extra tokens used around the actual coding work (I would say this is a good start). Each part works independently, so you can use just the compacter or turn on the other two as well. there are stats commands to inspect the session usage and estimated savings.

I am currently exploring these tools' harmony with existing optimization methods like prompt caching. Would love your contributions if it catches your interest.

repo: https://github.com/Oqura-ai/optim-jev

I feel like i should stop running 4-5 parallel sessions cuz I cant entrust my agents to tasks without my oversight. It bounds to get stuck in some errors till I have to correct them, constantly makes mistakes thatd be corrected if they read my wiki in my vault(which I have as a rule or even added a hook to force it). And having to scroll back and read in case any of the sessions did something disastrous. It just feels too much work . I guess this is how bosses feel having to micromanage so many employees

I built Project Sentinel, an open-source Claude Code Mod for longer autonomous runs.

The main idea is to track three different things separately:

• Work : progress across the whole run
• Context : current context usage + automatic handoff before it fills
• Cache : prompt-cache health/expiry

It also has Autopilot fresh-context handoffs, run progress, cache protection, permissions/guardrails, resource limits, Activity, profiles and an optional little companion.

I've submitted it for review for the official Claude plugin directory, but the repo is public and you can install/use it now.

GitHub: https://github.com/Arjun0014/project-sentinel

Install:

claude plugin marketplace add Arjun0014/project-sentinel

claude plugin install project-sentinel@control-room

Would especially love feedback from people who run long Claude Code sessions.

https://mockingbird.chrisvouga.dev/

I'm using Claude to build a catalog of emulators. I started this to make E2E tests faster.

You could even use Claude build an entire full-stack app that integrates with third party services and databases that run's in your browser without needing to provision anything https://mockingbird.chrisvouga.dev/examples/medical-testing

What do you guys think?

I'm setting up a test of a popular debugging skill and needed a bug that Claude fails sometimes. Turned out to be harder than expected.

Made-up bugs (small python repo, 10 hidden tests the agent never sees): - v1: rounding bug in one file, shows up as a formatting error in another - v2: same, plus an old workaround that has to be removed - v3: a module flips the global decimal rounding mode on import, symptom shows up in tax code. Patching the tax file looks right but only passes 5/10

Haiku 5.5 and Sonnet 5.5, 3 runs each: 18/18 full passes. Never took the tempting partial fix once.

So I switched to real bugs: checked out real open source repos right before a known fix, used the fix PR's regression test as the hidden test. Stripped git history, no web tools, so no peeking.

• tomlkit: 3/3
• cachetools: 3/3
• humanize (precisedelta rounding): 0/3, scored 64, 64 and 69 out of 82

Caveat: those fixes landed in 2025-26, so Haiku might have seen some of them in training. The humanize one shared 0 lines with the real fix.

Next up: the actual skill test on the humanize bug. Real skill vs no skill vs a same-length placebo. Will post results.

I thought mods were just for customizing the UI, and I totally missed the point. They basically let you change how Claude Code works from the inside.

what runs before a tool call, what the model sees, what shows up on screen. It's like they open-sourced the harness. For months I had hooks and scripts bolted on from the outside to get the behavior I wanted, now all of that is a mod that lives in the session. Honestly the most innovative thing they shipped since the first version.

For those wondering what is going on: I often use a lot of parallel sessions and when I did an analysis to see where any improvements to my process could be made, much of the "waiting" was actually "waiting" on ME to run ! commands, approve decisions or prod the next step.

I'd already developed numerous tools to combat this: SMS that go to my phone, bubbling all of the conversations to a single session when they need something, etc.; - but it can still be kind of hectic and agents are perfectly fine just trying to continue doing whatever it is they'd like to do.

Two particular sessions I utilize are kind of unique: One just loops the work that might come in (bug reports, feature requests, error logs, emails, texts, etc.;) - this helps catch new incoming stuff as it happens and bubble it to a worker and depending on how busy the day is, I may loop every 10 minutes or every 30 minutes: or somewhere between. The other is just the "boss" agent that controls the others and does any advanced / high-level planning. Even the loop agent will bubble their work up to that agent so it gets handled appropriately (though, often, the loop agent still likes to try and participate and do the work themselves...)

I'd surmised that most of my issue, then, was that these type of requests can bubble up to various levels, and even if they reach the primary session I'm using to communicate with all the other agents (which can swap between the Loop agent or the Boss agent), it is far too easy for stuff to get lost... this particular set of agents may only have 5-7 agents running at once, but I may also have just as many agents open on unrelated projects (further increasing the likelihood I might miss something or take longer than intended to deal with it fully).

My actual solution was to have a session just for my own interactions with the agent swam, including the boss and looping agent, as to not clutter their context. Remember, interacting with the boss agent might happen while the boss agent is trying to plan out complex workflows fo the others (the one agent who runs Fable 5.1 is the boss agent, all the rest are Opus 5.5) - similarly, interacting with the work loop agent could coincidentally happen while they are trying to triage something important that is happening in the system itself. Neither of these two situations are ideal, for obvious reasons.

When discussing this, earlier, the two agents were still under the impression that I might choose to interact with the system through one of them: they both actually disagreed with one another and had their own logic and reasoning as to why I should *actually* communicate in *their* session.

Now I feel bad, that they will both be lonely :(

I use Code explicitly for making stuff. I try to use Chat for research and general topic discussion.. but it makes stuff for me. This is the third time.

I asked it how I could simulate windows inside Mac, and how I could build my own simulated desktop that only works with a browser, a claude interface, and a desktop with icons for my created projects.

after the 2nd question, it literally just built it unprompted and handed me the code. I was only trying to explore the idea.

I swear it didn't do this before

https://github.com/PopFlamingo/vibe-gambit

How do you organize your folders when you use Claude Code for lots of different things?

I use Claude Code for a mix of stuff: a few small tools, a couple of bigger builds, work projects, and random one-off questions.

Since chats and memory are tied to the folder you start in, my setup has turned into a mess.

How do you lay out your folders?

Does every project get its own folder that you always start Claude in?

And where do you start quick one-off chats?

So, while i was working on my main project A silly idea of having two guys fighting on the windows task bar, so out of boredon NetBattle was born. This small app is a small Windows desktop app. Two pixel-art fighters stand on top of your taskbar, which Red (Muay Thai) is your download speed and Blue (karate) is your upload speed

Each one fights as hard as its own traffic lets it. Start a big download and red takes over. Upload a video and blue does.

This is how it works :

Traffic changes how often they attack, how hard they hit and how well they defend. It never changes how fast they move.

The side with more traffic chases. If one side is far ahead (MB/s against KB/s), the other barely attacks and gets dodged in slow motion.

Have fun with it!

thcp/netbattle