u/thatguydrinksbeer

The setting used to be called predictive speed assist or something like that. Also - I agree with you on one-pedal. It isn't more energy efficient, it's worse than coasting and using regen when you actually need to brake. Also, you won't be the doofus whose brake lights are constantly flashing.

Lol

That's no cloud, that's the HOA mothership.

I've been working on something similar for software dev, but with more of a hybrid approach: short conversations, frequent fresh sessions, and persistent memory of the final state. So far I've found that carrying forward the distilled state instead of the full conversation works really well.

FWIW: https://github.com/a-hansen/bonsai-dev

Outland and High Noon

Upstart Crow. Silly and clever comedy about Shakespeare. The last episode though...

You're on your way to something like this: https://github.com/a-hansen/bonsai-dev

This is it (on the main floor, not the mansion), La Partage as well. More often it's $50 min, and higher on weekends.

If I nope out of a friendly battle because it is dragging on, will one of us have to poke to resume the ping pong?

Friend your your clan-mate, then poke (attack) him. You should be able counter each other unlimited after that, well that's what I told above. The players I used to counter with haven't figured it out yet. *Edit - it works.

Thank you!

How many counters per day without tickets? I think I only get 5.

2023 was the year after Jack In The Box acquired them, transition phase probably.

Lots of shills too.

Wouldn't that be Hamburger Hamlet?

Not going to poke holes, just a solved problem: https://github.com/a-hansen/bonsai-dev

Exactly, too much context causes many problems, you want focused relevant context.

Start new prompts often; externalize the important memory and reload that at the start of each session. Once you start that, you will then have to deal with drift and scope creep. There are solutions for all of that.

↑

lol, Yahoo acquired, so I still have my geocities email because of that. But.so.much.spam I can't use it. Wish I could cleanse it, would be a badge of honor.

Also - use the web UI for design / planning.

I can’t speak to whether your account is bugged, but one thing that helped me a lot was changing the coding workflow so every prompt does not have to carry the whole project in its head.

Keep a small project memory in the repo instead of relying on chat/session memory. Requirements, architecture, current state, next step, open questions. Markdown is fine.

Start fresh sessions more often. The trick is having a good handoff note, so the new session can reload the project state without needing the entire previous conversation.

Separate planning from implementation. Before the agent writes code, have it say what it intends to touch, what behavior it is preserving, what checks it will run, and what is out of scope. Then only implement after that looks right.

I’d also keep an out-of-scope list. A lot of agent waste comes from useful-but-not-now ideas turning into extra work inside the same session.

Use cheaper/smaller prompts for mechanical steps and save the strongest model for design, debugging, and tricky implementation. Not every step needs the expensive brain.

Code maps help too. Even a short map of the important files/modules can reduce how much rediscovery the agent does every session.

None of that fixes a real quota bug, but it does make usage feel less random because each session has a smaller, clearer job.

Fair enough, here it is:

https://github.com/a-hansen/bonsai-dev

And yes, I think that same idea applies here. Bonsai has a human gate at major API and subsystem boundaries. The implementing agent first writes the interfaces and contract tests that demonstrate the intended usage, before it fills in the implementation.

The point is not just “write tests.” It is to force the design to become visible before the agent starts piling behavior on top of it.

I’m mostly looking at this through a software development lens, so I’m not claiming this solves general memory. But I do think the core problem is the same: memory should not mean dumping more stuff into context.

A useful memory layer has to decide what deserves to become memory, what is just temporary context, and what should stay out of the model’s way entirely.

That is the direction I have been exploring. Not another RAG wrapper, but more like selective project memory: requirements, architecture, current state, phase plans, decisions, and handoff notes, kept in human-readable files and loaded only when relevant.

The goal is not to give the model everything. The goal is to keep it focused.

In other words, memory should behave less like a search engine and more like disciplined project context management.

I don’t want to spam my own GitHub project here, but it is in my post history. Or just ask and I’ll share it.

BTW - done, thanks for the idea.