Newsfeed

In reply to @noahzweben · Feb 24, 2026

Announcing a new Claude Code feature: Remote Control. It's rolling out now to Max users in research preview. Try it with /remote-control

Start local sessions from the terminal, then continue them from your phone. Take a walk, see the sun, walk your dog without losing your flow.

In reply to @SpringStreetNYC · Feb 25, 2026

In the past week, I've had lunch with, respectively, 5 friends of mine. All of them top-notch non-technical founder-types with solid track-records.

Each conversation quickly circled in on AI claws and how they're experimenting with it, including the development and operations part. I LOVE that they're finally enabled to do this on their own and I love seeing that creative/hacker-y spark in their eyes. It feels like they've waited ages for a technical sparring-partner that could deliver at the thought-of-speed.

I am so happy for them and some of their self-made products are impressive. Technically and product-wise.

What I also noticed, and that's a surprise for me, is that when they go into very deep detail on their firewall configuration, I feel sad because I feel they've been kinda nerd-sniped/FOMO'd into this rabbit-hole and I am not sure how and when they'll find their way out again.

PS: Hand-written by Alexis, delivered to Twitter by Alexis' nanoclaw assistant

In reply to @SpringStreetNYC · Feb 25, 2026

PPS: Here's how I used Telegram/nanoclaw to post this (and thus avoiding getting sucked into the maelstrom of my Twitter feed) - That is using the desktop/Chrome skill I created. That's running in a permanent VM alongside the assistant.

The editorial policy I've set in the skill is that nanoclaw is only there to help format and deliver.

In reply to @SpringStreetNYC · Feb 25, 2026

In the past week, I've had lunch with, respectively, 5 friends of mine. All of them top-notch non-technical founder-types with solid track-records.

Each conversation quickly circled in on AI claws and how they're experimenting with it, including the development and operations part. I LOVE that they're finally enabled to do this on their own and I love seeing that creative/hacker-y spark in their eyes. It feels like they've waited ages for a technical sparring-partner that could deliver at the thought-of-speed.

I am so happy for them and some of their self-made products are impressive. Technically and product-wise.

What I also noticed, and that's a surprise for me, is that when they go into very deep detail on their firewall configuration, I feel sad because I feel they've been kinda nerd-sniped/FOMO'd into this rabbit-hole and I am not sure how and when they'll find their way out again.

PS: Hand-written by Alexis, delivered to Twitter by Alexis' nanoclaw assistant

In reply to @SpringStreetNYC · Feb 24, 2026

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.

In reply to @SpringStreetNYC · Feb 23, 2026

What I do like is having a clear distinction between "This is the Claude Code conversation to build this" and "This is the WhatsApp conversation to use this"

In reply to @SpringStreetNYC · Feb 24, 2026

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.

Claude Code DocsOrchestrate teams of Claude Code sessions - Claude Code DocsCoordinate multiple Claude Code instances working together as a team, with shared tasks, inter-agent messaging, and centralized management.↗ code.claude.com

In reply to @SpringStreetNYC · Feb 23, 2026

That'd be one-time. The VPS is about 10€/mo.

In reply to @SpringStreetNYC · Feb 23, 2026

Add 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.

In reply to @RealistSec · Feb 16, 2026

@SpringStreetNYC @openclaw @virustotal @good_BOT_boi Oh! And if you haven't updated for a while, the old version also used to use the main session UUID + it's history to spin up every 'heartbeat' check in every 30mins - so if you had a huge session, that would consume all your tokens on a check-in too,

In reply to @SpringStreetNYC · Feb 23, 2026

Quick checkpoint: So far, getting a basic nanoclaw setup working with Claude Code + API key: ~7€

This includes:

• Bootstrapping the installation itself
• Setting up WhatsApp
• Setting up Gmail
• Setting up Calendar

In reply to @SpringStreetNYC · Feb 23, 2026

Wrapping my head around nanoclaw:

In my main Claude Code conversation - on the metal of the machine if you will - we're setting things up, writing code and adding skills and mcps and config files.

However, the execution, triggered by Telegram or WhatsApp, still always happens in a container with very few credentials directly available within the run.

So, it's like on one hand having a ssh-REPL to the system and instant deployment to production.

In reply to @SpringStreetNYC · Feb 23, 2026

Quick checkpoint: So far, getting a basic nanoclaw setup working with Claude Code + API key: ~7€

This includes:

• Bootstrapping the installation itself
• Setting up WhatsApp
• Setting up Gmail
• Setting up Calendar

In reply to @SpringStreetNYC · Feb 17, 2026

"So what are people actually using @openclaw for?"

Here's a snapshot of "our" last 2 hours. With absolutely minimal guidance, "Noa"...

• sent an email to switch tax advisors: compiled docs, emailed the new one
• researched legal insurance for Germany: compared providers, picked top 3, organized follow-up for tomorrow
• tracked a stuck package: found the issue, sent the fix

Token usage stayed low once I used @RealistSec's recommendation and emphasized "Hey, use a sub-agent for..."

In reply to @SpringStreetNYC · Feb 17, 2026

@nicktozi You're right!

First cron job I've set up on my OpenClaw assistant is: "Help me learn how to delegate tasks. Be my mentor who teaches me with small delegation exercises throughout the day"