We tore out the shortcut PAL was quietly taking through your conversations, and a whole cluster of chat weirdness went with it.
For a while, PAL was quietly deciding — before it even knew what it was going to do — whether your message deserved the full brain or a lighter, faster one. That guess was made from your first few words, which is a bad time to guess. "Create new" is two words and kicks off an entire project. We went ahead and deleted that shortcut entirely. There's now one path through every chat turn, with the complete instructions and the complete set of tools behind it, every time.
That single change swept up a pile of things you may have run into. Option buttons that showed up as plain text you couldn't tap? They're real buttons again, and the layout follows a rule now instead of a coin flip: a short either/or shows as a row, anything longer or with explanations shows as a list. No more cards hiding off the right edge of your phone. Project creation that felt like it hung? PAL was actually working — it just had no way to tell you it had made the thing. It can say so now. And conversations that seemed to forget what you'd just agreed on hadn't really forgotten; two separate timing bugs were swapping in an empty thread behind your back. Your conversation follows you now, even when the project around it changes. While we were in there, we also fixed tapped cards getting stuck on "Sending" forever, and stopped PAL from occasionally answering your screen-size question with a build request.
A few days earlier we'd chased down the turn that could go quiet for the better part of a minute and then reply twice. Three separate things were tangled up in that one: PAL's understanding of what a motion or color sensor actually gives back was wrong, so its own code wouldn't pass its own checks and it would loop trying to fix something unfixable; every bit of thinking-out-loud along the way was getting glued onto the final answer, which is why it read like PAL repeating itself and asking two questions at once; and there was no ceiling on how long a turn could churn. All three are handled — you get the padding while it works, then one clean answer, and turns can't run away anymore.
Two more from that same stretch. Our pre-release testing environment turned out to be unable to run a single one of PAL's server-side tools — they'd fail silently into nothing while PAL patiently retried, which is where some of those two-minute pauses came from. Fixed, and it means the stuff we check before shipping to you actually gets checked now. We also caught PAL suggesting projects you'd already built, sometimes ones it had suggested itself last week. It was reading your project list as inspiration rather than as history. It knows the difference now, and it's got a temperature dial so ideas vary a bit more. Separately, PAL finally learned that it has a clock available when writing code for you — metronomes drifted and melodies stumbled without it, and generated music scripts got noticeably better once we told it. We also wrote down what a warm, musical sound actually needs from the hardware, which is groundwork rather than something you'll hear today.
The short version: chat should feel steadier. Fewer dead buttons, fewer silences, no more losing the thread mid-project.
If any of these were bugging you, thanks for saying so — nearly all of this started as someone telling us something felt off. Keep it coming.