Johannes Schickling

Just recorded this little performance demo of @overtone_app while working on my talk for @localfirstconf. Near-zero query latency enables a magical UX.

@fmzakari Very cool! Nice work!

$ORIGIN is coming to binfmt_misc! fzakaria.com/2026/07/20/lin… relocatable binaries for #nix #nixos #nixpkgs are in our grasp.

@bohdanbirdie @threepointone 🔥

As promised, here is a demo of ESP32+DO💡 ESP-32 -ws-> DO <-ws- web-clients Might share a link later. There are few more goodies, like the sticky notes being filtered with Workers AI model and rejected and other stuff. Look like a nice surface to add agents to ESP screen🖥️

An Effect-First Frontend Framework: @foldkit @devinjameson joined @schickling on Cause & Effect to talk about Foldkit’s schema-first approach to frontend state, how it differs from React, and why this architecture matters even more in the age of AI-assisted coding.

Wish more leaders would join with this voice in nixpkgs.

Fun fact: Aaron aka @funkytek co-created Gulp.js back in the days 👀

I’ve been exploring ontologies as the “intent programming language” over the past few months as input/context for software factories. Worth a read - very interesting new frontier!

@nikolasburk Wohoo! Congrats on launching!

I'm launching LearnChess on Product Hunt today 🥳 It evolved from "an app I built for myself" to a passion project with an organically growing user base. After several months, I'm happy to share it with a wider audience! 🙏 An upvote would mean a lot: producthunt.com/products/learn…

@MichaelArnaldi @ZachWarunek @EffectTS_ Let’s do it! @ZachWarunek I’ve DMed you :)

@ZachWarunek @EffectTS_ Sounds like a great topic for Cause & Effect, cc @schickling

I love that I finally got to ship something to prod that’s fully written in @EffectTS_

Never thought I give @Steve_Yegge a shoutout. He was just early, like most visionaries. Now everyone is building factories.

@bohdanbirdie Nice! cc @DavidKPiano

An alternative to state machine graph visualizer, but with real interfaces in place. When agents change the flow you can see exactly how the user journey changes and what bugs floated. Easy to prototype changes too! Now, count how many times I said `reason` and `state` 😁

@jeffbarg @NotionHQ Thanks! Curious what speaks most to you?

@schickling @NotionHQ This is sick!

I’ve been very fortunate to collaborate with @NotionHQ over the past few months as a Hacker in Residence. Recently I built a OpenClaw alternative that lives within Notion and has access to all my tools like OpenClaw has. It’s working super well and I use it everyday!

Having your own personal podcast (infra) is incredibly useful. I use it a lot every day. I'm even re-republishing some podcasts to my personal feed with ads removed etc.

@NotionDevs @geoffreylitt Highly recommend reading this great post by Simon Willison! simonwillison.net/2025/Jun/16/th…

@NotionDevs Thanks for the nice chat @geoffreylitt! Will share more demos/improvements over the coming days! Would love to hear thoughts/feedback! Happy to answer any questions!

"Computa look at my calendar and book my usual spot to catch up with my friend for lunch this week. Send him a text when you complete it." This isn't a dream. Agents securely tool calling can now be done utilizing Notion. Here's how: > Notion agent connects to a secure local Openclaw > Portable memory powered by Notion agents > Sandboxed read access through custom tool calls In 12 minutes, our hacker in residence @schickling chats with @geoffreylitt to breakdown how he's approached the problem, demo a few use cases, and describes where he sees this going.

@bohdanbirdie @geoffreylitt 🙏

I really like how the access boundaries are discussed here, something that held me from using agents outside of coding. Will dive deeper into lethal trifecta article and Notion developers platform. Thanks @schickling @geoffreylitt!

@m13v_ @NotionHQ I've been using SCG with OpenClaw for about 5 months and it's been working great!

@schickling @NotionHQ the real test is a long unattended run: SCG vs a hard per-action gate side by side, and see which one you mute first ;)

@m13v_ @NotionHQ Yeah, I fully agree. Approval-fatigue is real, that's been one of the key insights that lead me to build SCG and one of the main things I disagree with about the design of OpenClaw.

@schickling @NotionHQ when you do try it, the thing to feel out is whether the per-action approval stays lightweight or turns into click fatigue on longer runs. that's usually where unattended agents live or die.

@m13v_ @NotionHQ Sounds like we came to similar conclusions! And yeah, Runner looks really interesting - wanted to check it out for a while. 👀

@schickling @NotionHQ routing access through SCG is the right instinct. once it can touch gmail + icloud the hard part flips from reach to which actions you let it run unattended, and that per-action gate is exactly what Runner bets on.

@m13v_ @NotionHQ Great point but that's exactly what I'm going for with my SCG setup. It's helping me to structure everything in a way where OpenClaw/Blocky has access to everything needed in a safe way. It already has access to my Gmail / iCloud files via SCG. It enables a lot of use cases!

an agent that lives inside Notion works until the task needs the file in your Downloads or a thread in Gmail. what governs whether it finishes is reach past the one app, not the tools inside it. Runner spans across your local files and services to close runner.now/?utm_source=s4… written with ai

I’m very excited about the potential of this and will share more experiments, demos and improvements over the next few weeks! Would love to hear your feedback and thoughts! 🙏

and needs approvals for anything potentially dangerous. This makes it incredibly ergonomic to use for most tasks while being secure by default. I’ll be sharing more about the details on this soon!