In reply to @SpringStreetNYC · Feb 23, 2026Add to that about 4€ for creating a new mentor-like "role" that I want openclaw to "play" and setting it up with a daily cron-job.
So, ~11€ in total in Claude Code API credits.
Honestly, this feels right. I actually now think that a lot more onboarding flows should be chat-based and Claude Code was, again, just a solid partner. Walked me through the steps one-by-one, fixed problems quickly.
Pretty impressed.
Alright - just keeping a tab on getting a nanoclaw assistant to a point where I feel like it's okay to stop fiddling with the setup:
Yesterday, I had precisely 125€ in Anthropic API credits. The basic nanoclaw /setup and /customize yesterday came in at around ~15€.
Then, running /setup-telegram, testing out agent swarms and building a simple status-dashboard that I can access from my laptop added another 20€.
So, I've spent ~35€ so far and still feel like I'm getting fantastic value.
And, what I LOVE about nanoclaw is the clear separation between using Claude Code for setting things up, customizing them, running ops etc. vs. using the Anthropic API for running the actual assistant(s).
Currently, I'm using Anthropic's Agent API for both, Claude Code and the assistants.
Given how I'm using Claude Code to build/setup/ops the system, I feel it would be fair use to use my Pro subscription here instead of paying directly for API tokens.
And given how the Pro subscription (as someone on HN wrote a few days ago) is, after all, like a ticket for one person to an all-you-can-eat buffet, I feel it would not be cool to use my Pro subscription here and it's totally right to pay for API tokens.
So, these are some of my thoughts here from today.
Next up: Since agents are run in ephemeral containers (yay!), I'm currently having Claude Code build me a separate docker container that runs a persistent desktop environment (KDE FTW) that will include a Chrome browser that both, I (via SSH/VNC) and the agent (via CDP) will have access to and can use.
