It honestly seems good enough that it might cannibalize Macbook Air sales.

My current goto for desktop apps is Tauri, which give us a rust backend and TS fronted (usually React). Local ML features can be easily loaded as a python sidecar. Production bundling can be a little challenging but it seems to work well so far.

Sidenote: Golang is also an amazing language for LLM use, I generally do most of my "infra" stuff in Golang over Rust, but either work fine most of the time.

I'm looking into how to structure my work to run some autonomous-safe jobs overnight to take advantage of it.

My main goal is to maximize my subscription token usage while trying to comply with the rules, but its not clear where the line is for automation so I feel like I need to be clever.

- regular development (most token use): all interactive claude mode, standard use case

- automated background development: experimenting with claude routines (first-class feature, on subscription)

- personal non-nanoclaw claude automations (claude -p): uses subscription token, but only called as needed (generally just fix something if something in my homelab infra goes does down, its set up to not fire on an exact cron time)

- other LLM based automations: usually openrouter API key, cheap models as needed

- nanoclaw: all API key based, but since its expensive I keep usage mostly minimal and try to defer anything heavyweight to one of the other automation strategies (nanoclaw mainly just connects my homelab infra with telegram)

For context: I have additional automation with scripts set up on the mini, some of them call LLMs to do things like summarizing today's news.

I have other automations that are agentic and just run "claude -p" (mainly just checks status of other jobs and fixes them automatically). Agentic automations are great because they can handle unexpected situations (at the cost of predictability). They're all sandboxed and we have control over tools for the most part. Any files it would write to are typically git-controlled so we have change records and rollback built in.

Nanoclaw acts as an agentic layer but combines it with the communication layer over telegram to make it interactive.

I use it to go through my centralized task list (currently beads in my main 'wiki' monorepo), give me nudges for todos, I can also send it pictures of say, food and it will fetch a recipe and sort it into the wiki via a general "inbox" skill (claude has it as well). Every day at 12:30 it will give me a mini "standup" of all my personal projects and todos, and once in a while will give me some thoughts based on my interests.

Its set up to do appropriate tasks with local models to keep token costs down, so far it doesn't seem to cost more than $10-20/mo, it would use less if I didn't drive it with sonnet.

I'm still experimenting with it, and trying to go slow, one thing at a time. I don't give it access to anything super sensitive yet, and try to keep it observable.

I literally did this 12 years ago based on this reasoning, its good you're trying to counter that with the next generation.

With that said, I do wish there was more discourse around systemic issues rather than the usual finger-pointing towards rival social groups. Unfortunately I feel like our language gets in the way, systems issues are more abstract, but "bad people" are more visceral and easy to talk about.

It doesn't solve the problem of general LLM dependency (at the end of the day we gotta keep our brains sharp), but any LLM-based workflows aren't all of a sudden put at risk if we set up something that depends on it.

I do think there would be value in sharing your setup at some point if you get around to it, I think a lot of builders are in the same boat and we're all trying to figure out what the right interface for this is (or at least right for us personally).

My bull case for this is that Nathan Fillion and crew have had 20 years of exposure to this fact and likely know what they're getting into and how to do it right. The only question is if they'll be able to execute. I'm excited!

We're discovering so much latent demand for software, Jevon's paradox is in full effect and we're working more than ever with AI (at least I am).

https://brightpath-global-solutions.com/

Edit: repo link: https://github.com/chronick/global-business-solutions

- declarative-ish UI in typescript with react

- rust backend for performance-sensitive operations

- I can run a python sidecar, bundled with the app, that lets me use python libraries if I need it

If I can and it makes sense to, I'll pull functionality into rust progressively, but this give me a ton of flexibility and lets me use the best parts of each language/platform.

Its fast too and doesn't use a ton of memory like electron apps do.

- I can build SPAs with typescript and offload expensive operations to a rust implementation that targets wasm

- I can build a multi-platform bundled app with Tauri that uses TS for the frontend, rust for the main parts of the backend, and it can load a python sidecar for anything I need python for (ML stuff mainly)

- Haven't dived too much into games but bevy seems promising for making performant games without the overhead of using one of the big engines (first-class ECS is a big plus too)

It ended up solving the problem of wanting to use the best parts of all of these different languages without being stuck with the worst parts.

Or maybe ask yourself what do you like to do outside of work? maybe build an app or claude skill to help with that.

If you like to cook, maybe try building a recipe manager for yourself. I set up a repo to store all of my recipes in cooklang (similar to markdown), and set up claude skills to find/create/evaluate new recipes.

Building the toy apps might help you come up with ideas for larger things too.

So for your example, yes you might tell the agent "write a fantasy story" and you might have a "storytelling skill" that explains things like charater arcs, tropes, etc. You might have a separate "fiction writing" skill that defines writing styles, editing, consistency, etc.

All of this stuff is just 'prompt management' tooling though and isn't super commplicated. You could just paste the skill content into your context and go from there, this just provides a standardized spec for how to structure these on-demand context blocks.