Bitcoin
I save in Bitcoin. This is where I explain why and collect the resources I would share with someone curious. — Why I save in Bitcoin
Back to Home
daily
daily
daily
daily
daily
daily
daily
daily
daily
experimenting
daily
daily
occasional
occasional
experimenting
experimenting
daily
daily
experimenting
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
daily
Notes
What I’m using, learning, and spending time on. AI tools, Bitcoin, my church, and the projects I’m building. I update this page when something changes.
Away from the keyboard · Models · Harnesses · Interfaces · Evaluating · Subscriptions · Infrastructure · Tools•Updated
Away from the keyboard
Faith, Bitcoin, and the things I keep coming back to.
Truth Chapel
My church. Livestreams and teaching are available on YouTube. — Watch Truth Chapel
Models
The raw horsepower. Seven models, pinned ⌘1–⌘7 in T3 Code.
Claude Fable 5
dailyanthropic · model · default
My default. The model behind most of my Claude Code sessions — the one I hand the large, context-heavy, repo-shaped work to.
+ Strongest at planning and long sessions
+ Careful on niche problems
Claude Opus 5
dailyanthropic · model
The everyday Anthropic model when I do not need Fable — fast, precise, and still the one I trust for tight, deterministic output.
+ Quick and reliable for routine edits
+ Same harness, lower cost
GPT-5.6-Sol
dailyopenai · model · second opinion
The heavier of the two GPT-5.6 variants, and my go-to second read through Codex — a different angle when Claude and I keep circling the same answer.
+ Useful contrast to the Anthropic models
+ Good at reading a repo cold
GPT-5.6 Luna
dailyopenai · model · opencode go
The lighter GPT-5.6 variant, run through OpenCode Go. Fast into focused edits when I do not need Sol.
+ Fast into implementation
+ A lighter option for routine work
Kimi K3
dailymoonshot · model · opencode
Moonshot’s model, run through OpenCode Go inside T3 Code. A different read from Claude and GPT without leaving the same loop.
+ Open weights
+ A genuinely different read from the big two
GPT-OSS 20B
dailyopenai · model · opencode · ollama · local
The fast local model running through OpenCode and Ollama on my home 3090.
+ Private and local
+ Fast enough for routine work
Qwen3.8 27B
dailyalibaba · model · opencode · ollama · local
The smarter local option on the same 3090 when the job can afford a slower pass.
+ Private and local
+ More capable than the fast 20B option
Harnesses
The agent loop itself — the thing that takes a model, gives it tools, and lets it inspect a repo, edit, and run checks. Claude Code and Codex each run their own vendor’s models; OpenCode runs anything. The interface I drive a harness from is a separate choice.
Claude Code
dailyanthropic · cli · coding agent
My default harness for high-context, repo-shaped work — planning, larger edits, and longer sessions where keeping the whole repo in view matters. Runs the Claude models; I drive it from T3 Code or Warp.
+ Strong at planning and repo-shaped work
+ Holds context across longer sessions
- I still pair it with Codex when I want a second read
Codex
dailyopenai · cli · coding agent
My implementation-and-inspection agent: fast at reading the repo, making focused edits, and running the test/check loop. I drive it through T3 Code or Warp, often as a second read against Claude Code.
+ Quick into implementation and repo inspection
+ Clean inside T3 Code and Warp
- I reach for Claude Code first on the largest, most context-heavy tasks
OpenCode
experimentingopen source · cli · coding agent
The open-source harness, and the only one of the three that is not tied to a single vendor. I run Luna and Kimi through the Go plan, plus GPT-OSS and Qwen locally through Ollama on my 3090.
+ Vendor-neutral — any model in the same loop
+ Same repo workflow as the other two
- Still deciding how much work it earns next to Claude Code and Codex
Interfaces
The surfaces I sit in front of. An interface hosts a harness; it does not replace one.
T3 Code
dailyinterface · multi-harness · daily driver
Where I spend most of my time now. Not a harness — it sits on top of Claude Code, Codex, and OpenCode and lets me run any of them from one window, with seven models pinned to ⌘1–⌘7 so switching is a keystroke instead of a context rebuild.
+ One interface over three harnesses
+ Switch models and harnesses without leaving the flow
- Warp still wins when I just want a terminal
Warp
dailyterminal · interface · daily driver
The terminal, and the second surface after T3 Code. Anything that is not an agent session — git, deploys, the odd CLI run — happens here, and it is still where I drop to when I want the raw CLIs. — my referral
+ Keeps a real terminal in the loop
+ Works naturally with both major CLIs
- Still learning where Oz fits alongside it
Claude desktop
occasionalanthropic · desktop app
Mostly for chat — conversation and thinking out loud rather than repo edits, which stay in Claude Code. In the rotation, but a smaller share of my week than it used to be.
+ Good for conversation and thinking out loud
- Not a replacement for Claude Code on repo work
Codex desktop
occasionalopenai · desktop app
Where my scheduled tasks live. Recurring jobs run here on a timer while the interactive Codex work happens in T3 Code.
+ Scheduled tasks without a server or cron to babysit
- Little reason to open it outside the schedule
Evaluating
Tools I am testing against my real workflow before promoting them to daily-driver status.
Oz
experimentingwarp · cloud agents
Warp's cloud-agent orchestration. Same family as my daily terminal, so I am testing where cloud agents fit next to Hermes and the local CLIs.
+ Fits the Warp-centered direction of the stack
- Still forming an opinion on when to reach for it
Hermes Agent
experimentingnous research · orchestration · command center
Nous Research’s agent harness, self-hosted on the VPS. It can coordinate Claude Code and Codex as workers and take work over a Telegram gateway, all over Tailscale rather than the public internet. For me it is the remote and async lane — a job I can kick off from my phone — while most real work still happens locally on the Mac.
+ Remote control from my phone via Telegram
+ Private by default — no public exposure
- Still deciding what actually belongs in a remote lane versus the local loop
Subscriptions
The paid plans that make the stack work — a different kind of thing from the agents and models they unlock.
Claude Max
dailyanthropic · $100 plan
The plan behind my Claude Code, T3 Code, and Claude desktop usage — enough headroom for the heavier, repo-shaped sessions.
+ Room for longer Claude Code runs
- Still deciding how much belongs in desktop vs. CLI
ChatGPT Pro
dailyopenai · $100 plan
The plan behind my Codex work and GPT-5.6 access. I am still confirming the cleanest public-facing name for the exact Codex tier.
+ Makes Codex a real daily agent instead of an occasional backup
- Naming around the Codex tiers is easy to make too messy
OpenCode Go
experimentingopencode · Go plan
The plan behind OpenCode and my Kimi K3 access. Cheap enough to keep a third harness in the rotation without thinking about it.
+ Puts an open-weight model in the same loop as the big two
- Only earns its slot if OpenCode does
Warp Build
dailywarp · Build plan
The terminal plan behind my second surface.
+ Worth it for a terminal I open every day
- Oz is still in the evaluating bucket for me
Infrastructure
Where the work and the sites actually live — the local box, the always-on box, hosting, and DNS.
M1 MacBook Pro
dailyapple silicon · local environment · hardware
Where the work actually happens. Not an AI tool, but the machine the harnesses edit on and the checks run against, and the default over the VPS for nearly everything. Still plenty of headroom for the whole stack of CLIs, editors, and a browser at once.
+ Handles the full local toolchain comfortably
+ Quiet, cool, and always ready
- Heavier model and container work still belongs on the VPS
Hostinger VPS
dailyhostinger · KVM 4 · Ubuntu 24.04
My always-on server — a Hostinger KVM 4 box on Ubuntu 24.04. It complements Cloudflare rather than replacing it: Workers stay the default for public web apps, while this runs Docker workloads, private tools, background jobs, and Hermes. Access is private-first over Tailscale, with only SSH and HTTP/S exposed publicly. — my referral
+ Always-on home for self-hosted services and agents
+ Private-first access over Tailscale keeps the surface small
+ Cheap, predictable place to run long-lived processes Workers are not meant for
- I own the patching, backups, and uptime myself
Cloudflare Workers
dailyhosting · next.js · opennext · edge
Where my public sites live, including this one and morningportion.com. Next.js apps ship through the OpenNext adapter, so the same App Router codebase runs at the edge instead of on a Node server. Static things skip the framework entirely and deploy as plain assets. Moving here from Vercel put hosting, DNS, storage, and access control on one bill and one dashboard.
+ One platform for hosting, DNS, KV, R2, and access control
+ OpenNext runs a normal Next.js codebase at the edge with no rewrite
+ Static sites deploy as assets with no framework overhead
- The Workers runtime is not Node, so some npm packages need a compatibility flag or a swap
Cloudflare Access
dailyzero-trust · auth · sso
How my private apps stay private without building auth. A one-time-code login sits in front of the whole origin, so tools like my workout logger and a few family apps are reachable from any device but open to nobody else. It is the reason those projects can be genuinely useful to me and still never expose a login form to the internet.
+ Real access control on a personal project without writing an auth system
+ One-time email codes mean no password to manage
+ Applies to the origin, so nothing leaks if a route is forgotten
- Anything behind it cannot be shown off without a separate sanitized build
Cloudflare DNS and Registrar
dailydns · domains · registrar
My DNS and domain registrar — the layer that points every domain at Workers, the VPS, and everything else. At-cost domain pricing and fast DNS make it the quiet foundation under the whole stack.
+ At-cost domain registration with no markup
+ Fast, reliable DNS for every property
+ Single place to manage all my domains
Tools
Companion utilities and helper surfaces that support my workflow.
Superwhisper
dailyvoice · dictation · macOS
Push-to-talk dictation surface. Hold the hotkey, talk, release — audio is transcribed then processed by an LLM mode of my choice. — superwhisper.com
+ Push-to-talk hotkey makes voice feel like a real input mode
+ Choose transcription and processing models independently
+ Modes for verbose dictation, summarized meeting notes, and clean prose
- Mode customization takes a beat to internalize when you build out more than a couple
Obsidian
dailynotes · vault · editor
My personal knowledge vault and note-taking surface; central to workflows and long-form drafting.
+ Local-first, extensible with plugins
+ Great for Zettelkasten-style linking
Tailscale
dailyvpn · network
Zero-config mesh VPN that keeps my machines and VPS reachable securely.
+ Simple secure networking across devices
+ Works well for remote agent access
Helium Browser
dailybrowser · privacy
Lightweight browser I use for isolated browsing and testing; useful for quick checks.
+ Fast, minimal surface for quick browsing and testing
Codex Bar
dailymenu bar · codex
Menu-bar runner for quick Codex prompts and snippets without opening the full app.
+ Convenient for one-off prompts and small snippets