1,450 karma · joined August 4, 2012
Writing https://leanpub.com/aismarthome
It'll assume I own a datacenter and have lots of gpus just because I asked to research things.
Also a Bluetooth dongle in my attic about 40ft USB cable. Works great for home assistant too and Bluetooth devices like plant sensors outside the house over ble
Bonus points if you do tailscale and jetkvm or wake on LAN and can moonlight from anywhere.
Its annoying but with Claude and a little knowledge you can make it persistent. By default it got wiped every update which was annoying.
"Use this CLI tool and figure it out. Look up this sentry issue using it"
"Add a service that watches for an error in the log. Look at the home assistant MCP data and find my phone, send a notification to it and make it send when there's an error"
Now after it manually does it and makes the code. "Make this into a skill for anytime I paste a URL with sentry inside the message"
But also important: "make that procedure a prompt file so when I invoke it I just pass X after it and it works fully"
Having too many skills for things that are very specific where you can directly invoke it via slash command, wastes context space with the skill headers I find. So I make those prompts instead
I hacked the spec to pass through a cookie via the oauth handshake to do this without needing an oauth server.
Its really dumb they don't want to allow this.
If no cookie, open webpage.
If cookie set, close and persist.
I literally wrote an 80 page mini book on MCP yet it frustrates me to no end.
it's also not even complicated:
Copy my ssd to an external ssd so i can boot from it.
Opus did this just fine.
Fable planned to have me reboot to safe mode. ok thats fine. I told it no.
It started copying and overwriting the ssd while IN PLAN MODE. this is crazy it feels so dumb vs the marketing
I have a base container.
"A" to make a new instance.
Pi.dev when I hit enter on any container. Hot swap anthropic enterprise and openai and openrouter as needed.
Every container has the dev env already running for my current projects. Iterate, rarely use vim when needed, spec driven and have llm draft prs for me then I review.
I know the codebase in and out so what I want done is on bypass mode and then I review closer at the draft PR step before marking ready for the team.
Vibe coded in 30mins a textualize tui that shows lxd containers.
I just hit "p" on a container to forward that container to host.
I only use ports for one instance at a time so it works perfect.
Hitting enter auto joins the lxc container instance with tmux.
Works perfect for me for tasks that can stay long running
I create a draft pr and manually review all items before then marking ready for review for the team.
So I'm not blindly pushing things to prod without review.
Without staging key access I wouldn't have been able to do a payment provider migration at this speed. iterating by migrating users in staging and being able to use and validate the sdk quickly with opus is a massive time saver.
I hit 'n' to toggle all network access minus anthropic and openai URLs.
I use pi (sometimes claude, always on bypass) and I auto allow everything. I only toggle manual approval in rare cases like running a script or command that needs to touch a production system and I need to validate everything.
Normally my container has full write access to staging so it can debug and validate everything on its own
The real cost effective way is giving a team $20 cursor $20-100 Claude $20-200 codex.
I'm spending 1k on Claude enterprise easily and that's with trying to spread it on codex and cursor using pi.
Cursor team Codex team Claude team
Swap between the models when limited.
I am saving our company a lot of money vs Claude enterprise usage cost
i use gpt 5.5 and opus 4.7 a lot every day, if i can get good results at this speed, hopefully the usage level holds up on my team plan haha