As developer I'm using Claude in IDEs and running may tasks a day and every time have to set Ultracode on. Wouldn't it be nice to have an option to set Ultracode as default, unless I'm missing something and there are settings like that.
1 man show, I gather requirements shape the stories do the tickets, set the rules, do the architecture, design whatever.
Now I get a new baby software developer. I don't know which part to hand off to them? What do I do? They'll be completely new to Claude, because we work with high security usually, so this will be a first. What do I pass and what do I keep? I don't know where to draw the line because I have no lines. Guidelines please? How does your work look like?
I built this, so full disclosure: it’s my project.
Most reviews are written in the first week. Regret usually shows up around month six. So I spent about 2 months building Regret Radar, which gives products a Regret Score from 0 to 100 based on what owners say after months and years, not on launch-day hype.
What it does:
- 421 products across 46 categories, from AirPods to air fryers to the Vision Pro
- Every researched product cites its real sources. No made-up quotes or fake Reddit users, and if something hasn’t been measured, the page says so.
- A satisfaction timeline from day one to year two, plus hype vs reality
- Personal scores: answer a short quiz and every product gets a second score for you, with the reasons spelled out
- Gift mode, compare, and live web checks of what owners are saying right now
- Owner reviews that nudge the score, with safeguards so brands can’t rig their own products
It’s free to use, with no ads and no data sold.
I’d love feedback, especially if you think a score is wrong on something you own: regretradar.com
I really feel like this is kinda more complicated than it needs to be. I loved it before where you finally could select model effort with the slider, see usage and context (with the stacked bar graph showing what is messages, mcp etc) in one go/ area. I feel like this is a step back.
Is there a way to customise it to go back or is that something only anthropic can do?
kimo is a free, open-source (MIT) video editor with no GUI. Your agent drives it over MCP from Claude Code, Cursor or any MCP client: cuts, color, keying, tracking, captions, keyframes, audio, transitions, and now 3D scenes. Runs on CPU.
Working on building a GUI next to see the agent live in action.
I went through the claude code docs this morning instead of the changelog and found a few things about why long sessions eat your limit that I hadnt seen posted anywhere.
the main one.. your prompt cache lives for an hour on a subscription while youre inside your plan usage. the moment you go past that limit and start drawing on usage credits, the main conversation drops to a five minute ttl. same session, same work, the gap you can leave before a cold reprocess just got 12x shorter. on an api key or a cloud provider its five minutes by default from the start.
everything that isnt your main conversation already gets five minutes regardless. subagents and workflows and compaction and session titles. so a subagent you come back to after ten minutes reprocesses from scratch even on a max plan tbh.
the fix is prob one setting. promptCacheTtl set to 1h, or the CLAUDE_CODE_PROMPT_CACHE_TTL env var. subagentPromptCacheTtl covers the rest. needs v2.1.242 or newer. api key users can set it too.
two other things I didnt know. switching models mid session reads your entire history with zero cache hits. if you run opusplan then every toggle in and out of plan mode counts as a model switch, so bouncing between planning and building rebuilds the cache each time. agent teams also run roughly 7x the tokens of a normal session when teammates sit in plan mode, which the docs state as a plain number.
run /usage and look for the Prompt cache (main) line if you want your own hit rate. needs v2.1.251. on v2.1.260 and up it also names the likely cause of your last miss.
My issue, I forget what CLI / TUI tools I have installed that I can practice using, and add to my workflow. Used a simple prompt to create a stupidly simple html file with all my CLI tools and example usage. Also, this helps me remove things I don't use.
Prompt (modify as you need):
My challenge is that I keep forgetting CLI / TUI tools I have installed on my machine and sometimes forget their usage. My package manager is brew. Go through the list of tools `brew list` and get info for each tool using `brew info`.
Get the CLI tool name, URL, and summary of its capabilities. Finally, a section showing common usage examples. For example, for `fd`, an example like `fd logo -e png` would be helpful, with a one line short description. Please skip CLI installs that are used purely for backend use like `abseil`, which is a package of common C++ libs.
Output Format: Create a simple webpage. Use the fastest simplest css stack, nothing fancy. Add a quick search. Mobile responsive.
I struggle to hit 20% of my weekly quota with Opus 5.5 and I've been trying to give it some tough tasks. The power at my disposal is starting to finally sink in and I'm having trouble keeping the pipeline full so to speak.
At a point of considering "vibe-coding" very large chunks of my projects now since maintainability on some things doesn't really matter, or I just need somebody to do the hard part (like port old stuff) so I have a place to start.
I wouldn't do it for anything important, like anything that takes credit card or has privacy/security issues, or actually needs to grow and be bug-free.
Still. Maybe English really is the new programming language.
Just got approved for 5 premium seats for startups. i dont have any employees. how do i use the other 4? do i need 4 new devices or is there an easy workaround to keep it on one device? Will t3code work for account switching and is it grey area which will violate their tos?
I'm James Luan, CTO of Zilliz, the company behind the open-source Milvus vector database. These are notes from using Claude Code on our cross-platform database build.
The lesson I kept returning to after using coding agents on our cross-platform build was about the target I had given them. Getting the code to compile on one machine and making it work across supported environments were different engineering problems. The agent could satisfy the narrower request without knowing the broader one existed.
That distinction matters when building infrastructure for other people. A personal project can optimize for the author's machine and familiar edge cases. A distributed system has to preserve behavior across platforms and components that a single patch may not describe.
Some of the hardest production bugs we encountered were syntactically valid changes. The missing information was an assumption about how several components were supposed to coordinate. It was absent from the diff and existed only in a developer's mental model. The AI review approaches we tried did not catch those bugs.
That is why I put so much weight on explicit constraints and tests that express system behavior. They give an agent something more useful than an instruction to produce cleaner code. They also give a reviewer a concrete way to challenge whether the requested change actually solves the whole problem.
A passing local build is evidence about one environment. Turning that into confidence for infrastructure users still requires an engineer to identify the assumptions that the build never tested.
Claude Code's auto memory loads one MEMORY.md index into every session, up to the first 200 lines or 25 KB, and reads topic files when it needs them. That works early on. Mine grew to 305 files over three months of daily use, and catching up at the start of a session meant reading 267 KB.
What I changed:
The index holds three things: open work (one line each), one line per rule, and pointers. It stays around 17 KB.
Child indexes by area. Each lists the topic files for one area of work, and Claude opens it only when the task is in that area.
One topic per file. Current facts at the top, every change dated.
History goes to an archive file. When a file passes about 30 KB, its dated notes move word for word into a _log.md file next to it. A small script does the move, then rebuilds the original from the two files to prove nothing was lost.
A study hook. I start each session with MEMORY.md study plus the task, and a UserPromptSubmit hook tells Claude to open only the index and the files for that task.
Result: a session now reads 18-67 KB instead of 267 KB, and no fact has been lost in a split.
So I wrote plain English instructions for a sub-agent, a "Problem Finder", which an agent automatically spawns after it finishes work. The Problem Finder sifts through the logs of what happened, and records problems.
It worked great! I was able to discover and fix a whole host of issues that I wouldn't have otherwise known about.
I'd add features, change things, and all was good. Then I added a feature that broke a couple things.
As usual, the agent spawned its Problem Finder to review the logs. The Problem Finder found the issue, and reported it.
But it turns out the feature I added also broke something with the Problem Finder. It had its own problem. So, it spawned another Problem Finder to sift through it.
The new Problem Finder found the issue. It reported it, being the good agent it was.
But it ran into the same problem itself. And so it spawned another Problem Finder to research the issue and report it.
This continued, recursively, over the course of maybe 1-2 hours until my account ran out of tokens for the session limit.
So I had to change the text. It now stops at "problems related to problems with Problem Finders", so at least I get the one level deep.
Find every Claude Code session on your computer, recognise each one at a glance, relaunch it with a click, back sessions up, and export chats. Windows / macOS / Linux.
Unofficial community tool — not affiliated with or endorsed by Anthropic. It only reads the transcript files Claude Code already keeps on your disk; nothing leaves your machine.
Four agents can finish four pieces of work at once. I cannot make four decisions at once, although opening four terminal windows provides a convincing impression that I'm attempting it.
I run persistent coding-agent seats across dedicated machines. Claude Code handles implementation and complex integration, Codex does much of the review and repair, and I route other work according to the job and the remaining subscription quotas. The organisation around them is called the Weave.
The interesting part has become what happens after an agent writes the code. Who reviews it? Who fixes the findings? Where does a lesson go so the next session doesn't repeat the same mistake? And why am I still the person copying messages between windows?
I've built quite a lot of machinery around those questions. Here's the useful part.
A ticket becomes work, not another notification to me
I organise work in Linear. Hive is the broker connecting it to Slack and the agents' machines. Each machine has an edge process; a dispatch gives the selected agent a brief and starts or resumes the work.
I originally routed tickets with bespoke labels. Then I built AI Usage to track the allowance across my subscriptions and feed that into routing. I actually started writing the old explanation for this post before remembering I'd replaced it. Apparently this is what happens when you write a setup guide while still changing the setup.
Claude Code is doing real repository work here: reading the code, implementing changes, running checks, opening pull requests and responding to reviews. I spend the more constrained model capacity on integration and judgement, rather than every mechanical edit.
The agents review and repair each other's work
The automated pull-request loop is called the Belt. A different model reviews the change, and its acceptance belongs to the exact commit it examined. A new commit needs a fresh decision.
Findings go to a fixer session. The fixer reads the findings and the relevant code, makes a coherent repair, and returns the new head for review. I don't need to carry “the reviewer found a bug” from one terminal to another.
There is a stopping condition. If the loop isn't converging, it stops with a specific question for me and a separate diagnosis of what went wrong. I have no interest in paying for an argument whose only stopping condition is the next rate limit.
One expensive lesson: an agent would correctly identify a structural defect, explain the right fix, then defer it as a “design change” and patch another symptom. Several review rounds later, we were still discussing the same defect. The standing instruction now is to change the construction that keeps permitting it. Explaining the fix is not doing the fix.
Lessons have somewhere to live
We call recurring lessons scars. They become shared procedures with concrete completion criteria, or executable checks in the repositories.
Some checks inspect syntax trees: package boundaries, where models may be constructed, and where model-name constants belong. That moves a recurring review argument into a check the next agent can run.
Agent Affordances is the collection of small tools built around this work: structural duplicate and reuse discovery, compact Linear reads, a bounded model coprocessor, and the Attention launcher. They're separate command-line tools, so you can take the piece you need without adopting my entire setup.
One output of this workflow: the live valuation explorer. Stored facts are outlined; the blue overlay shows a counterfactual.
The rule I care about is simple: a failure should leave the next session better equipped to handle it.
The human needed a queue too
Hive Attention is a durable queue of interventions that actually need my judgement: a product decision, an architectural tradeoff, or choosing which generated face resembles the person in the reference photographs.
An agent submits a self-contained brief: what it needs, the context, the artifacts, and what my answer will unblock. The current Slack interface sends one message for a new request and updates that card in place. I choose when to pick it up; a model finishing doesn't switch my active project for me.
The Slack surface has controls for the intervention. My response is saved and routed back to the originating work, either into the bound session or with the saved context explicitly restored. The waiting agent doesn't have to occupy an execution slot while I think.
We've now demonstrated that return through the working Slack interface. This is the bit I'm particularly pleased with: the decision, its context and the continuation belong together.
The portfolio and system map connects the larger enterprise work—Sokrates, the Krepis operational ledgers and Morphe's typed interfaces—with the smaller tools and products. The 13 October inventory covered 50 repositories and 95 named packages and applications; the full counts and method are there.
Three pieces I'd particularly like people to look at:
Agent Affordances, above, is the immediately reusable part of the workflow.
ConceptStudio puts dataset preparation, concept-focused captioning, review, remote GPU orchestration and LoRA training into a native Mac application. Its source is public. Alongside it, H3Forge provides ComfyUI nodes for MiniMax H3 video generation, including sparse attention and timeline/reference prompting.
Residual Modeling serves an Icelandic apartment-price model you can use in the browser. The estimate is decomposed into property, location and time effects. Change a property input and the counterfactual overlay shows how the estimate moves. The underlying project covers collection, matching, feature assembly, training and serving.
The range is why I care about reusable engineering procedures. A useful review process shouldn't need reinventing because this week's project has photographs in it rather than payroll records.
For a smaller setup, I'd start with one implementation session, an independent review, an explicit stopping condition, and somewhere for the lessons to go. Add routing when there is work worth routing.
The question I keep coming back to is: why did this need me?
Sometimes it needs a product decision or a judgement call. That's work I'm happy to do. Sometimes I was just the mechanism connecting “review found a bug” to “someone should fix the bug”. That's a fairly expensive use of a human, even one who is already sitting at the computer.
I always have way too many Claude Code chats open across a few accounts. The annoying part was never the work itself. It was coming back to a chat an hour later and realizing it had been sitting on a permission prompt the whole time, while I thought it was still going.
So I built DHI Orbit. It's a small page that runs on your own laptop and puts every chat on one board:
which chats need you (questions, permission prompts, stuck jobs, chats that hit a limit)
which ones are actually working
each account's 5-hour and 7-day limits
a reply box on every chat, background ones too
It only reads Claude Code's own files on your machine and replies through the normal `claude` CLI, so it never touches your login. Nothing is hosted, it stays on 127.0.0.1, and leaving it open costs zero tokens.
If you want to try it: `pipx install dhi-orbit` (brew and pip work too), run `dhi-orbit`, and open http://127.0.0.1:8787/. It's MIT and just the Python standard library.
It does read Claude Code's internal files, so an update can break something. When it can't read a number it shows "?", and if you hit that, tell me and I'll fix it.
Hey guys, not sure if this is helpful to you or not but I thought I would share as it has been an absolute game-changer for me.
If you pop this into your global CLAUDE.md file:
```
What I need from you
End every turn where you're blocked on me, or where the next step needs me, with a short "What I need from you" section. Numbered, one concrete action or decision per item: exactly what to do, where (which site, app, file or person), and what to send back. e.g. "Open the Convex dashboard, add OPENAI_API_KEY under Settings > Environment Variables, then reply 'done'", not "I need the API key set up".
If there are several, put the quickest or most blocking one first, and say what you'll get on with in the meantime.
If you don't need anything from me, say "Nothing needed from you right now", and say whether the work is finished or still going.
Never bury a request for me in the middle of a long update.
```
Then reading and understanding what Claude needs from you next becomes sooo much easier.
This for me has been one of the biggest bottlenecks when working with claude (and to a lesser degree other agents) trying to understand what exactly they need from me to continue progress.
With this I can quickly decide what to do next or potentially end this thread.
And that word "decide" I think is critical because I think thats what "coding" boils down to these days, making decisions, as many as possible as quickly as possible.
I'm making FrogPop, a Bubble Trouble-inspired game where a frog pops bubbles with its tongue. I posted it here in August. This is a new clip with the rebuilt crab boss and some of the powers.
Claude Code helped build the tongue attack, splitting bubbles, waves, shop and boss systems. My usual approach was to describe one mechanic, have it read the relevant C# scripts, then try the result in Unity.
One thing I had to change was asking it to check the saved scene settings before editing code. Unity can have a value saved on a component that overrides the default in the script. Changing that default can look like a fix without changing what happens in the game.
I now keep that instruction in the repo, along with preserving prefab references and keeping changes small enough to test. I still have to check the result in Play Mode.
I also use Codex for fixes and art integration. Some art is AI-generated and then edited. The recent art pass took a lot of revisions, especially getting the bugs to look right at game size.
I can confirm that the issue seems to have been resolved today. However, we've already burned through a significant portion of our weekly quota because of it.
Personally, I have four days left until my quota resets, with only 30% remaining. Most people in the original thread reported similar usage issues, although there were some differences from one user to another.
Even if usage is back to normal now, the damage has already been done. Those of us who experienced unusually high usage are still left with depleted quotas for the rest of the week.
Anthropic shouldn't just fix the issue and leave it at that. Given the impact on users, I think they should make another gesture to compensate those affected.
The new Claude Projects is driving me insane. I used to see a permissions toggle but it's gone. It keeps stopping on small tasks that the old projects, code or co-work handle swiftly. I give it a request, whether it's in the thread, or overall project chat and then it doesn't do it and gives me *Another* prompt I have to paste which I don't realize if I'm working on other tasks across Claude Code.
Sometimes it'll even do it right after using Chrome extension. Then I question it "How can you not use browser? You just did" and it's like "oh you're right, change permissions" then next message "Actually it's your mac" then it'll go back to saying "It's not your mac"
I’m one of the founders of DronaHQ. We kept seeing the same thing: teams build internal tools fast with Claude Code or Cursor, then get stuck at hosting, auth and database credentials.
So we built the DronaHQ MCP. From your IDE, the agent can:
deploy front-end apps into a hosted runtime
push JSON configs that become live APIs, webhooks, scheduled jobs or workflows
bind to SQL, NoSQL, REST or gRPC connectors whose credentials stay in a vault, so generated code never holds a secret
Everything lands behind SSO, role-based access and an audit trail. Admins control which users get which apps, which devs can build for which teams, and which apps can reach which data. It runs on our cloud or self-hosted.
I’m doing a live build tomorrow (Fri Oct 16, 3–4 PM PT). also you can signup and try build app for your enterprise. The first 10 people to ship to prod & submit will get a chance to win AirPods 4. Challenge and theme to be posted tomorrow when I open the page. https://luma.com/ps4ti0oh
