Hacker Newsnew | past | comments | ask | show | jobs | submit | zackify's commentslogin

Self made TUI that just lists LXC containers.

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.


Haha that's what I do personally.

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 vibe coded a TUI that just shows running lxd containers

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


Sounds like your process has made you vulnerable to huge classes of exploits and accidents. You have no oversight of changes locally, and only focus on when it touches prod. That means toxic local changes can get in, and if it works in staging why would you look too closely at it before merging to prod? Meanwhile a malicious npm package has made it into your repo, and your staging api keys have been sent to the command and control server.

i can view the diff locally but often times after planning with opus i get what i want.

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.


As someone who negotiated 4 day weeks since early 2020 its been awesome. I get chores and yard work done and more family time every week. Wish it was standard.

We are on it at my job. It saves money due to other parts of the org not using as many tokens.

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.



Best deal currently:

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


Can they please do this with at&t internet.


+ and Adobe Creative Suite


this thing is so awesome on fast mode, so far i am impressed, some of its observations feel similar to opus.

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


and this is why i use pi.dev and hotswap models and have no reliance on a single provider


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: