Founder, Metacube Digital · building https://xitter.cf/t.co/p9HrVd5r54 Product studio in Vancouver · web, mobile, AI Design & build for founders & small teams · DMs open
Remote/Vancouver
Joined April 2024
- Tweets90
- Following54
- Followers4
- Likes328
🤔Paying for Cursor Pro+ and don't see it on list of plans anymore
Cursor is now part of The X Subscription.
Current Cursor subscribers can keep their plan or switch to The X Subscription.
Paid plans share one usage pool across Cursor, Grok Build, and other Grok products, with twice the coding usage on Grok models as the equivalent Cursor plan. Premium, Super, and Ultra also include Grok Bot.
To make room for more Grok usage, third-party models in Cursor move to API pricing on the new plans. We'll keep working to make your usage go further, with more compute, better inference, and more token-efficient models.
The X Subscription is available at cursor.com/pricing.
using AI to productize site builds felt kinda dirty at first.
then it clicked: the taste calls were always the job. the grind was just expensive.
cutting grind without shipping sludge is the actual craft now.
where do you still refuse to let the model touch?
day job is still the hard product stuff. prototypes, weird ui, apps with edge cases.
on the side we figured out a marketing site package we can ship without it turning into sludge. spare capacity + picky process, not a pivot into web-mill land.
do you keep a simple offer next to the complicated work or does that just confuse people?
two ways i keep seeing studios sell sites:
big custom build, then radio silence
or leaner launch where someone actually owns what happens after
if you’ve bought either: which one didn’t waste your money?
trypepper.ing/ starting to look pretty good but some things I feel are not refined enough and the copy is still a bit awkward in some places. Let me know what you think.
I claimed @dima on OpenShaders and got my one-of-one shader. What will yours look like? openshaders.com/@dima
Fantastic news, thank you for the performance fix my M1 MBP was starting to struggle with all the work I was doing 😛
Traycer v1.3.0 is live! 🚀
🌐 In-app browser - a browser panel inside the task that you and your agents both drive.
📥 Session import - bring your existing Claude Code, Codex, and OpenCode sessions into Traycer as first-class tasks.
⚡ Performance - large chats and workspaces open faster, with a lighter memory footprint.
💬 /btw and /side - fork a question into a side chat while the original keeps streaming.
🐬 Reasonix - the Reasonix provider is now supported.
📄 PDF preview - open PDFs directly in workspace.
🔔 Notification chimes - customize the sound effects for app alerts.
🧹 Sweep - clean up the leftover worktrees across every machine.
And a lot more! Changelog for detailed changes 👇
github.com/traycerai/traycer…
I can’t seem to figure out an S tier workflow for my agents to compare native built screens with the Claude design files. The flow right now with maestro and screenshot comparison feels C tier at best.
dima retweeted
Good Sunday. Reset has been propagated to accounts and we landed some fixes to usage for things mentioned yesterday as issues we found. You should feel a positive difference. More to come tomorrow and will keep communicating.
Update on rate limits in Codex.
We’ve found (a) some inefficiencies when using images in long sessions with multiple compactions (b) high p95+ usage for Computer History (c) a feature that was meant to generate conversation titles that was draining a bit more usage than intended. And we have a tiger team combing through everything and shipping fixes tomorrow. We also found a novel approach to drive efficiency up significantly that is completely unrelated and we will be working on next week.
As part of some of the fixes tomorrow, we will also do a full reset of the usage for all paid subscriptions.
See you then.
dima retweeted
Update on rate limits in Codex.
We’ve found (a) some inefficiencies when using images in long sessions with multiple compactions (b) high p95+ usage for Computer History (c) a feature that was meant to generate conversation titles that was draining a bit more usage than intended. And we have a tiger team combing through everything and shipping fixes tomorrow. We also found a novel approach to drive efficiency up significantly that is completely unrelated and we will be working on next week.
As part of some of the fixes tomorrow, we will also do a full reset of the usage for all paid subscriptions.
See you then.
Update on rate limits in Codex. We do see that for some users the cache hit rate has been worse this week than the stable state the weeks before. This could explain that usage is draining somewhat faster for those users as hitting the cache consistently is an important component of being efficient.
We are investigating and will have an update tomorrow.