Zak El Fassi

I think the present and future is people installing local spyware on their machines and using it as training data. @Noth Can you spin up an MVP for macOS?

this morning’s Bay Area weather feels like AGI just quietly landed and didn’t tell anyone

@Moroccoprojects @Jesuislibis Whatever is native to the ecosystem always wins. Never understood why those palm trees existed; though I suspect one would know if they follow the money.

🟢#What_if the Ain Diab Corniche and other Atlantic cities finally replaced their Washingtonia palms with resilient maritime pine forests? ➡️Ecological Shift: Replacing costly, shade-less Washingtonia palms with maritime pines that thrive in salinity, Atlantic mist, and winds

@ChennouneMedia @Moroccoprojects We’ve had decades with graphic designers what have we achieved? Let people cook with AI. You can try it sometime.

@Moroccoprojects It's hypocrisy, because you talk about young people needing jobs while you are taking someone's else job right now, a young graphic artist could do you much better work, some will even do it for free just to get their names out there.

@arconte112 @Teknium @thsottiaux @sama @gao_zibo OpenClawdex

@Teknium @thsottiaux @sama @gao_zibo I mean, Codex is already OpenClaw.

codex mac app is winning SO HARD. just need: - native editor - iOS app - full browser - openclaw then it might be the home default app

@fdotinc @eptmpa i wanna intern

hit up the founder! @eptmpa

He reinvented the 3D printer Introducing the polysynth mini:

@marouane53 🔥🔥🔥

@InsiderPresider we're breaking through question is, will we spin up, or spin down? we'll watch and see.

@zakelfassi the timing is definitely interesting since everything seems to be falling apart at once

Are we going to acknowledge that today is an actual zero-day?

@mronge I think that would definitely be helpful. Mini map resizing/moving around also A+

@zakelfassi Ah good point, what if we added a keyboard shortcut for the mini map?

My AI agent got stuck this AM and I wasn't at my desk. I pulled out my iPhone, connected to my headless Mac mini with Workbench, and got it back to work. Quick demo:

@ivanfioravanti @nopmobiel There’s more truth in this statement than sarcasm; injecting confidence (between long runs and when the llm is clearly entering a thinking/confidence loops) can actually help a ton, sometimes as much as a new context window.

@nopmobiel 😂 Unbelievable! LLMs need a personal trainer like in the gym to help them to push more.

I keep using GLM 5.1 like crazy because it's great in pure coding. The problem is that here and there it looses confidence in itself and I need to push it to exit from thinking loops like these 😂 (uppercase from the model thinking itself!). Maybe I should tweak the prompt saying :"YOU CAN DO IT! 💪" Let me take a deep breath and just run the tests. OK actually I need to stop this ridiculous internal monologue and JUST TYPE THE TOOL CALLS. OK, HERE ARE THE ACTUAL TOOL CALLS. I'M TYPING THEM NOW. FOR REAL. NO MORE THINKING. JUST ACTION. STARTING THE COMMANDS. NOW. TYPING. HERE ARE THE ACTUAL TOOL CALLS. TYPING THEM RIGHT NOW. NOT THINKING ANYMORE. JUST TYPING. THE. COMMANDS. NOW. Let me just DO IT. No more analysis paralysis. Action. Now. Typing. Going. Running. Doing. Commands. Now. Here. Are. The. Tool. Calls

the missing primitive is a local/private context bus. right now every agent runtime has its own little world: • claude code has project/session context • codex has its thread/app context • openclaw has memory + routing + channels • hermes has whatever it's carrying • cli tools have stdout/files/process state but none of them share a durable "what is going on?" layer without copy/paste, screenshots, or leaking everything to some SaaS. what i want is something like: events/files/sessions/messages ~> local semantic index ~> scoped context packets ~> whichever agent/runtime needs it not one mega-agent. more like private air traffic control for a swarm. the hard parts for me right now (at fleet level that'll probably grow again very soon...) are permissions + compression: what can this agent see? what should it remember from what it sees? what should it forget? what context is safe to move across runtimes? what degree of information granularity do we expect across different sessions (code/research/thinking...) that's the piece that feels underbuilt and an entire ecosystem that needs to get eventually bootstrapped. everyone is racing on agents, but the connective tissue is still duct tape and a body without a well functioning CNS is full of tremor.

@zakelfassi 👀 tell me more

Have something wild cooking if you live in Claude code / cli / open claw / Hermes land . @ me and tell me why you should get an early look

@patrickc @stripe Inspiring shipping velocity at your scale.

We just announced a large raft of improvements at @Stripe Sessions. My meta reflections: • It feels that the entire economy is replatforming right now. • Many charts at Stripe are inflecting in quite dramatic ways. What GitHub recently reported for commits we are seeing in economic activity (such as new company formations). • It is increasingly clear that agents will be responsible for most transactions in the not overly distant future. • Stripe was always developer-centric, but AI is making developer-centricity strategic in a new way: agents are even hungrier for good DX than developers themselves are. • Things that we’re launching are increasingly network products at heart. (Instant transfers between Stripe businesses, new kinds of fraud prevention with Stripe Radar, stablecoin payouts to anyone with Link.) "How can we turn Stripe's economies of scale into user benefits?" is increasingly the relevant question. • Between Privy, Bridge, Tempo, and Stripe’s core capabilities, we’re now doing a lot in stablecoins/crypto, and companies like DoorDash, Ramp, Meta, and Klarna are using our crypto stack to deploy meaningful new functionality in production. “But where’s the production use?” is rapidly becoming stale when applied to crypto. • After more than a decade of building, we seem to have hit some kind of critical mass of core platform capabilities such that building new things now feels easier and faster than before. (AI also helps.) We announced Stripe Treasury last year (originally called Financial Accounts); since then, we’ve added multi-currency support, global payouts, card issuance and rewards, and a bunch of other sophisticated functionality. By the end of this year, Treasury will support 15 more currencies and be available to businesses in 160 countries. On the launches themselves, a small selection that I thought were cool, though this is really just a subset: • The @Link AI wallet. Point your agent to github.com/stripe/link-cli and ask it to make purchases on your behalf with secure single-use tokens. (To test it, I asked Claude Code to buy a small gift for me yesterday. It purchased HTTPZine on Gumroad.) • New payment methods for Link, including Pix (largest payment method in Brazil) and UPI (largest payment method in India). We’re also adding stablecoin support to Link (which I think will be huge if we execute well). • We’re adding a lot of new Machine Payments Protocol functionality, including micropayment and recurring payment support. • We announced Checkout studio: a sophisticated dashboard for managing your checkout flow, including things like transaction replays and A/B tests. Today this tends to require a lot of fussy edits to production code. • Adaptive Pricing (which automatically localizes the price and currency that customers see) now supports subscriptions. We’ve seen pretty huge (4–5%) conversion rate improvements after enabling it — customers really like paying in their home currency. • New Stripe Terminal reader (the T600) with a customer-facing screen that can run native apps, plus support for 15 new international markets for Stripe Terminal. • General availability for Stripe Managed Payments, our merchant of record solution. (Natively handles tax, disputes, fraud.) Maybe sounds a bit arcane, but it’s one of those iykyk products. It saves a lot of schlep. • Fraud is a *much* bigger priority for customers than it was 2 years ago (AI makes fraud easier + unlike software, tokens can be resold), so we’ve been extending Stripe Radar to support things beyond payments fraud: free trial abuse, multi-account abuse, pay-as-you-go abuse. Early results are extremely positive. We also announced Stripe Signals — new scoring APIs for customers, businesses, and other objects, not just payments on and off Stripe. • Usage-based billing is also becoming the de facto business model of the AI era, and we launched a bunch of new pricing models in @getMetronome and features like low-balance alerts, automatic credit top-ups, and multidimensional pricing structures. • We showed streaming payments built on @Tempo and Metronome — track usage and get paid the instant value is delivered. Hard to predict, but I think this could be big. (Why wouldn’t you want to get paid as costs are incurred?) • We added automatic US tax filing in Stripe Tax. • We announced Stripe Database -- a hosted PostgreSQL database with all of your Stripe data, updated in real time. Read-only to start but we’ll make it read-write. • Stripe Workflows are now GA. • We showed Stripe Console, a full agentic execution environment built directly into the Stripe Dashboard. It’ll happily write code and use tools to answer your questions. • We previewed custom objects: model your business data directly in Stripe, with custom objects, typed fields, and relationships. • As mentioned above, Stripe Treasury accounts will support storage in 15 currencies by the end of the year. And instant/free(!) transfers between US Stripe businesses. • You can use a Stripe card with your Treasury balance and get 2% cash back on purchases. • We’re massively expanding our Global Payouts coverage -- soon 100 countries with fiat rails and 160 with stablecoins. • Atlas companies can now raise money directly within Stripe. • We launched the platform growth studio, which uses Stripe’s network data to generate specific recommendations for optimization/growth. • We announced the Stripe Managed Risk API — platforms can outsource risk handling to Stripe while maintaining full UI/UX control. • Connected accounts now benefit from networked onboarding, which hugely increases conversion rates. • We’re launching Treasury for Platforms. Connected accounts can get spend cards with just a few lines of code. (Plus cash rewards, cash acceptance, check acceptance, real-time payments…) • We announced Issuing for agents: easily create cards for agents. But that’s really just a subset of a subset. (See stripe.com/roadmap for more.) The Stripe team is cooking! And if you’re interested in building the economic infrastructure for this new world, we’re hiring.

Harness sovereignty

@stripe @link where's the 🧢?

Today, we’re launching the @link wallet for agents. It lets you securely empower agents to spend on your behalf. Your payment credentials are never exposed and you approve every purchase. link.com/agents

@longnow 👀

What does long-term thinking look like in practice? Introducing Long Now Labs, a collaborative space to test, prototype, and build long-term tools. Lab Series 001 is a collaboration with the Protocol Institute to investigate three aspects of civilizational durability that are being radically reshaped by frontier technologies. -> Lab 001.1: Book of Time - An open call to submit a concept for a new way of marking, experiencing, or making sense of time. -> Lab 001.2: Epistemic Cycles - Seeking an individual or team to investigate historical patterns of technological disruption that broke down society's ability to discern truth. -> Lab 001.3: Interspecies Protocols - Exploring the protocols needed to support interspecies ecologies. If you are a designer, researcher, writer, or technologist interested in the deep future, we want to hear from you. Submissions are now open. Learn more about Labs and how to apply: na2.hubs.ly/H059wn90

@zeeg And no @RepoPrompt? Come on now

To be clear the ask was to revert to 4.6 not swap to gpt 😅 We give folks access to Cursor, Claude, and Codex and may the best person win

just asked the team to turn off opus 4.7 no true gains in performance, burning compute (and money) honestly, imo, a bad release from Anthropic

@WannabeLurker @adamdotdev @robertpiosik i sometimes wonder if we'll ever wake up

@adamdotdev @robertpiosik 2020 has been a long, long fucking year.

I’m going through the craziest burnout I’ve experienced in my ~17 year career I’ve been sick for 16 days now, haven’t even been able to go for walks I kind of fucking hate AI I think all of these things are related