Entries for May 15, 2026

  1. Portrait of Onur Solmaz
    @onusoz · /2026/05/15· View on
    This is also my setup now, except - Instead of mac mini, I have a DGX Spark (asus variant) - I run openclaw alongside codex, and talk to my openclaw instance via discord
    @nickbaumann_·
    My laptop has become a “satellite device” since I started using Codex from my phone. And my Mac mini has become the “home.” It’s clunky, but the end state feels more like how we’re going to be working in the near future: I’m currently running the Codex app on 2 devices: 1. my MacBook 2. my Mac mini My laptop isn’t reliably connected to Wi-Fi enough, so I keep a Mac mini on my desk that is always connected. When I kick off new threads from my phone, I start them on the Mac mini. When I’m working from my desk, I run them there too. The cool part is that I’ve added my MacBook and Mac mini as connected devices to each other. That means I can start and resume threads from either device. So if I’m in a meeting but want to continue a thread on my laptop that was started on my Mac mini, I can do that. I’ve also set up mutual SSH for Mac mini <> MacBook, so files are easy to access from either side. It’s not fully seamless yet, but the model works. What this means: - I have an always-on Codex that is accessible from my phone, with its own dev environment - All threads are always accessible from any of the 3 devices - I can run heartbeat threads that stay on 24/7 It’s a little makeshift today, but the shape of it feels very real to me: Codex is no longer tied to whichever computer happens to be open in front of me. It starts to feel like something I can stay connected to across whatever device I’m using.
  2. Portrait of Onur Solmaz
    @onusoz · /2026/05/15· View on
    And what good is this for? It lets me program my claw @dutifulbob to extract signal from the noise, and display it in my personal open source news aggregator scoop I feed it discord messages, openclaw git history, and other various sources, and it's supposed to evaluate whether that content deserves my interest. it's still work in progress, because the more batched you process all the info, the worse it informs in the screenshot below, my claw underrepresented what Peter has done in one day 👎 on the other hand, it has also found a PR about local model discoverability 💪 Here is the system I use to aggregate all my info, still under development:
  3. Portrait of Onur Solmaz
    @onusoz · /2026/05/15· View on
    About creating an INTERESTS.md in OpenClaw I use my openclaw instance to aggregate all my news and information sources, including work and maintainer stuff Like: what did everyone do today? Did anyone had an issue with acpx today? Any complaints from users? I have various interests like this over different projects, and I've found out it's not helpful when I have all the interest info dispersed throughout my openclaw workspace To address this, I have created INTERESTS.md, which is automatically included in the context like AGENTS.md and SOUL.md. I define sections for each different context of interest, and in other news aggregation skills, I just tell it to "look at my openclaw interests in INTERESTS.md" and such
  6. Portrait of Onur Solmaz
    @onusoz · /2026/05/15· View on
    People were asking at @clawcon singapore how to setup eg. gemma with OpenClaw, and I realize for some time that there is no easy “1 click” local model deployment. Because local model landscape is constantly changing, and there is a million different ways you can do something For example you can use LM studio to load a model (llama.cpp), or you can use vLLM. Why would you choose one over the other? vLLM currently supports MTP speculative decoding, and it’s a work in progress in llama.cpp. There are so many knobs and dials you can adjust The first time end user of openclaw should of course not have to know about this! Having sufficient hardware that supports an open model, and not having an openai or anthropic subscription, it should automatically give you the option to set up a fully functional local model with a single click! If the current ease of setup of local models are around gentoo or arch linux level of difficulty, we should aim for e.g ubuntu/manjaro linux/omarchy level of difficulty i.e opinionated and easy first setup, with the ability to change all the configuration later on until I make all of this possible, you can start with the following: - read existing local models doc below - create a new channel in telegram or discord for testing local models. you don’t want to change the global default model just yet - tell your claw or coding agent to download and lm studio locally - tell it to download gemma4-e4b or gemma4-e2b and set it up on openclaw for the new channel you have just created. tell it to not stop and loop itself until it gets a successful response from that channel all these steps will be made redundant in the near future, but until then, this should get you going with experiments and getting a vibe check on the capabilities of open models. you can also copy and paste the contents of this tweet to your agent, and it should be able to set it up for you https://t.co/C0I9HK4Dj1