Denver sports and some Clawdbot
Sunday weblog notes from January 25, 2026 that were compiled and shared.
Today is a big sports day in Denver, Colorado. We are going to watch the Denver Broncos play the New England Patriots this afternoon and the Colorado Avalanche play some hockey today as well. I have the Altitude+ sports application booted up, and I’m ready to watch the game. The last couple of Colorado Avalanche games have been questionable, and the team went from being absolutely dominant to dealing with adversity. Sometimes they say that can help the team develop, but selfishly, I would have preferred to just watch dominant hockey all season long. This year I have had the chance to watch most of the games thanks to Altitude+, which has been a surprisingly good investment in terms of getting streaming access to almost all the games.
This was one of those weeks where my plans for productivity were rock solid and well articulated, but my actual writing output was subpar. That might be a bit of an understatement. My writing output for the week was lacking. I did, however, want to start playing with the new sensation setting my feed on fire this week, which is an open-source project called Clawdbot, which looks really interesting [1]. People seem to really like this thing and are even buying or setting up separate computers to run it all the time. I’m going to spend some more time digging into this one before I use any of the skill integrations [2]. The idea that people are just building and sharing all these skills for this open-source implementation is really interesting.
One of my biggest concerns of the whole agent race is just how powerful the integrations could become and how open they are to adversarial prompting and attacks. These types of ecosystems where people elect to connect more and more things to agents open the door to potential unintended consequences and bad actors. I’m sure it is one of the things that has slowed Google from allowing Gemini to just run wild across the broader ecosystem. One of the things I always consider the greatest potential risk vector is if people allow these things to make trades or take finance-related actions. Any mistakes within that type of finance workflow could be catastrophic. I’m going to try to set it up in a sandbox environment and not really connect it to anything impactful to kick the tires this week. I’ll let you know my thoughts next week about how that exercise ended up playing out.
Over the last few weeks, I have shifted to using Gemini more than ChatGPT, which has been interesting. I got really used to the ChatGPT application on my MacBook Air, and Gemini requires me to use a browser tab instead. I even went as far as to stop ChatGPT from loading at startup, which is a big shift in my usage. I was really curious about the personalized intelligence package they launched for Gemini [3]. We will see how that plays out going forward. Some of the personalization seems overly deferential and very repetitive in how it references concepts it wants to show you that it is aware of, which is off-putting. I write and work within a variety of topics, which seems to confuse the personalization they have so far running. Maybe they expect you to have a lot more deep work and focus on very specific things. I tend to research and jump from topic to topic each week. Like, for example, this week I’m very curious about that Clawdbot open-source project, but I may only be interested in it during the research phase.
Footnotes:
[1] https://github.com/clawdbot/clawdbot
[2] https://docs.clawd.bot/tools/skills
[3] https://blog.google/innovation-and-ai/products/gemini-app/personal-intelligence/