Michael Fransen

@FintechKristen @ajambrosino Weren't taxes due a few days ago? 😂

@ajambrosino You told me you were doing your taxes this morning.

Through hard drives and  migration assistant, my personal Mac has files and projects going back to middle school. Every project from college. All docs from almost a decade at my startup. Codex just explored and organized the whole thing– 20 years of files. Spent a lot of time this morning exploring. So cool.

@mattdorsey @SFPD @SFDAOffice Check out this video. reddit.com/r/BAbike/s/wdf…

The utter disregard for human life and safety this motorist demonstrated is shocking. I’ve elevated this hit-and-run crash to the @SFPD brass and @SFDAOffice. San Francisco needs to send a strong message that we won’t tolerate this kind of traffic violence and lawlessness. (1/2)

@Lincoln_Osis @rossweight @mattdorsey @SFPD @SFDAOffice 😬

@MichaelFransen @rossweight @mattdorsey @SFPD @SFDAOffice Yeah this is where I almost got rear ended yesterday by a guy going straight at the left turn lane. Bosworth and Diamond

@Lincoln_Osis @rossweight @mattdorsey @SFPD @SFDAOffice The cyclist has a green light. SF is doing this thing now where they tell cyclists in the bike lane to go with a green bike light and tell cars no red turn. They assume cars follow the laws which is hardly the case. At least in this neighborhood.

@Lincoln_Osis @rossweight @mattdorsey @SFPD @SFDAOffice I live near this intersection and am very familiar with it because of how dangerous it is. The van was following the law because there is a no right turn light there. The black car didn't want to wait so they actually went around the waiting van and then turned right on red.

@Mark_in_SF @mattdorsey @SFPD @SFDAOffice I agree. They are scary af as a cyclist because the majority of people turn right when the bikes have a green light. Unfortunately, this is what they are doing all along folsom now too. It also doesn't help that a lot of the no right turn lights are half burned out.

@mattdorsey @SFPD @SFDAOffice As a pedestrian, cyclist, and driver, I DESPISE these new streets with parking between car traffic and the bike lane, that requires cars to right turn across the bike lane instead of merging first.

@RichardManso3 @theslloyd @mattdorsey @SFPD @SFDAOffice correct.

@theslloyd @mattdorsey @SFPD @SFDAOffice so the vans had a right turn red light (intersection is "green for straight moving traffic, red for right turning traffic, green for straight moving bikes")? so dark car was running right turn red light as well?

@hspter @mattdorsey @kron4news It really is. Everyday you can find people stoped at red lights and then just driving through them if they don't see cars. People will do what they are allowed to get away with. 😢

@mattdorsey @kron4news the article doesn't even fully cover the extent of the illegal turn, because he purposefully changed lanes to pull around other cars waiting in the turning lane. I have had people honk at me for waiting for those lights as well. That entire neighborhood is a driving disaster

@mattdorsey @kron4news This is literally what is like riding bike everyday in Soma. Especially that intersection. 20% of people stop at the no right turns. Since there is ZERO traffic enforcement in the city, we should at least have cameras at all these intersections ticketing everyone.

I am informed that SFPD’s Traffic Collision Investigation Unit is on this case — and anyone with information can call SFPD’s Anonymous 24/7 Tip Line at +1 (415) 575-4444. Here’s the @kron4news story. (2/2) kron4.com/news/bay-area/…

@leerob @politepanic Does not work. That option isn’t available.

@politepanic Update to 3, Cmd+Shift+P, Open Agents Window cursor.com/docs/agent/age…

Meet the new Cursor! Very excited about this. Wanted to share a bit more of the story of how we landed here, how the product evolved, and some of the technical details on the new interface. I've been coding primarily with agents since Opus 4.5, but hadn't found an interface I loved (including our own). Agent sidebars or CLIs worked but still felt limiting to me. And our first iteration of the "agent window" wasn't good enough yet. So we went back to the drawing board to build a completely new interface for agents in December. The trend seemed pretty clear that increasingly less time would be spent in traditional IDEs. But as we started to dogfood early versions, it was very hard to give up some parts of an editor. Even if agents write 98% of the code, that last 2% of viewing files, debugging, many small edits and refactors, and having all the niceties like go to definition, LSPs, and more were really important. We couldn't remove those. So @ryolu_ and I started prototyping some ideas late Dec for a new interface. It would start simple/zen, but then allow you to still go deeper as needed. And slowly we developed enough conviction to make it real. The Cursor eng/product team then took some of those early ideas and made something 10x better than I imagined. Seriously major kudos to the team! We started fresh with this new UI in a lot of ways. "Deleting the product" is especially important as models continue to improve and the UX needs to be continually rethought. However that doesn't mean you have to throw out *all* the good ideas. Making it easy for existing users to adapt is also very important. In this new interface, we own all the pixels. We were able to design a system/architecture that takes all the learnings from Cursor 1/2 and moves away from some of the VS Code constraints we were limited by. I definitely empathize with feedback that in Cursor 2 we were moving around the UI too much and changing icons/buttons. Agents were taking over more and more work, and they started to break out of the IDE UI. We needed to iterate and try a bunch of things, and that was annoying for those of you expecting a more consistent editor experience. Making this new agent interface as a separate window actually also makes the Cursor 2.0 IDE *better*! Rather than continuing to try and extend the IDE to have agents own the entire UI, we were able to simplify and delete a lot of code by using existing VS Code patterns. Namely, agent chats are now just normal tabs like any other file. This is much more stable and familiar for doing splits/panes and all related keyboard shortcuts. A win-win-win, as they say. But also in this architecture refactor, we were able to address some local vs. cloud divergence and tech debt that had accumulated over time. The core Cursor agent harness is the same across the desktop app, web app, CLI, etc. So there really shouldn't be two code paths like: if (local) { ... } else if (cloud) { ... } Cloud agents were not used much until we gave them the ability to use a computer and record demos of their work, so now that usage has grown considerably in the past few months, it was even more important to nail this abstraction. We think cloud usage will continue to grow and be a big part of 2026. Finally (this is already a long post, oops), we have been able to really focus on performance in the new interface. I'm sure there will still be things to improve (please send them to us) but we've spent considerably more time profiling, investigating, and patching memory/cpu leaks. We are also now using the React Compiler! s/o @potetotes who has also been making a bunch of perf improvements. The end result here is that Cursor 3 feels much more pleasant to use. Faster, more reliable, less UI jank. You get to use all your favorite models, local or cloud, run automations, install plugins, get back demo videos, and more. Give it a try and lmk your feedback! We're gonna be shipping updates quickly in the coming days.

@conductor_build My coworkers that use graphite for stacking get nice branch UI. I don't use graphite and just manually stack prs. Is it possible to get this still? Or what is the suggested workflow for stacking?

@FintechKristen See ya tomorrow! 🛠️

Went to the beach after the king tides and big rainfalls in the Bay. Ended up looking like a ChatGPT advertisement; but at least here’s a timeline cleanse of someone not shouting very ignorant opinions about foreign or tax policy. Can we get back to work yet? Time to build.

@homsiT @ReadwiseReader @readwise - I am super confused. I have been a long time Readwise customer (paying). Today I go to reader and says I don't have access and that my trial expired. My credit card didn't change. What's up?

Awesome to see one of my recent projects getting such a great response!

@kane @DanielLurie Do we think it’s actually going to get to him?

I hope new SF mayor @DanielLurie focuses on fixing the deficit and crime and vetoes this boondoggle of a city bank, grandfathered in by the same corrupt supervisors who broke the budget.

@krishdotdev Claude, hands down.

You have $20, what will you choose ?

Reluctantly came back to X in hopes of staying more on top of AI happenings.

@mattpocockuk 💯

Claude Code with and without plan mode is night and day No plan mode: code is so bad it's basically a liability to keep it Plan mode: basically as good as I could write it, with occasional bugs which I catch on review Indispensable

@garrytan I feel like most people know this though. Even people that aren’t that tuned in. It’s basically a grump old man’s blog. Let’s all just be happy we aren’t as miserable as Tim.

48 Hills is not independent, is extremely partisan, and publishes misinformation to the detriment of the people of San Francisco