dbmikus

4 ms·

1.
by dbmikus 5d ago
For my example where I modify both the OSS and private repos, I sometimes have one agent coordinate both changes (maybe with subagents), or if the work is modular and separate, I have disjoint agents do the work separately. That said, most
2.
by dbmikus 5d ago
Restoring memory is useful if, when you resume an agent VM, you want the apps to be in the exact state when they were suspended. But for most things, I find resuming with memory is more trouble than it's worth. If you always resume fro
3.
by dbmikus 5d ago
Not sure about billions, but companies doing evals or RL or training will create really big bursty agent workloads. I think they are the best fit for AX, as opposed to individual dev teams building software, etc.
4.
by dbmikus 5d ago
I think it will be, but I don't think you need a standalone machine! If you run things inside a VM, you can get safety and control over access and networks A standalone machine is nice if you need more compute resources or if you want
5.
by dbmikus 5d ago
I'm working on something in the "cloud VMs for agents" space[1], so I have some battle scars and opinions! IMO, you want the flexibility to create either: (a) permanent devbox VMs, and (b) per-task VMs Agent sandbox platforms
6.
by dbmikus 8d ago
Now that is one vibe-coded website
7.
by dbmikus 10d ago
If you need xcode or macOS specific stuff, our VMs are all currently Linux based We're working on a "bring your own computer" feature which lets you take a spare Mac and slice it up into devbox VMs you can access from the clo
8.
by dbmikus 11d ago
Thanks! Have definitely appreciated your feedback as a user
9.
Show HN: Amika – Multiplayer cloud workstations for coding agents and humans(amika.dev)
6 points by dbmikus 11d ago|3 comments
10.
by dbmikus 14d ago
That's a good point!
11.
by dbmikus 14d ago
Pretty close, but IMO not quite. A math proof in and of itself is useless unless either: (A) it furthers human knowledge (B) it gets used in applied sciences, engineering, etc. If you merge and deploy code, you have released a to
12.
by dbmikus 17d ago
An AI-generated solution always provides two pieces of info: 1. proof that there is a solution 2. a solution that you can work backwards from to build understanding Maybe the solution is pretty inscrutable, but it's almost
13.
by dbmikus 19d ago
That is close to the average rate of inflation, though. Doesn't seem unreasonable to me.
14.
by dbmikus 20d ago
> I'd love to have exe.dev, but running on my Mac Mini. I'm working on exactly this bit (with some more tuning for messaging AI agents) https://github.com/gofixpoint/amika Doesn't run on your Mac Mini
15.
by dbmikus 27d ago
I haven't paid super close attention to Orbs, but I also build an agent runtime + orchestration layer on top of remote VMs ( https://github.com/gofixpoint/amika ). I do think it's smart marketing to name the co
16.
by dbmikus 1mo ago
For a truly "handoff-able" session, you also need to store the data it was working on. In most cases, these are the git patches
17.
by dbmikus 1mo ago
I'm working on this at my startup, amika.dev Open core is here: https://github.com/gofixpoint/amika We're designing it like a meta-harness actually. The goal is to let users put any agent(s) (Claude, Codex, P
18.
by dbmikus 1mo ago
Big enterprises are on a different github deployment, so I doubt they are affected by this
19.
by dbmikus 2mo ago
Agreed! I think the best user experience is: 1. You can run sandboxes locally 2. You can control them securely over the internet, for when you're on the go 3. You can migrate them to cloud VMs if you want If I can toot
20.
by dbmikus 2mo ago
What's your problem with the OpenCode config? My startup ( https://github.com/gofixpoint/amika ) copies agent configs into local or cloud sandboxes We run OpenCode currently, but need to improve the setup for users,
21.
by dbmikus 2mo ago
If you'd be open to trying something else, my startup is open core: https://github.com/gofixpoint/amika The definition for your cloud sandboxes is just a TOML config in your repo We also have an API and CLI to let
22.
by dbmikus 2mo ago
My startup is open core: https://github.com/gofixpoint/amika We run cloud sandboxes, and have some experimental local sandbox support that is fully OSS. Main thing for amika.dev is you can control the sandboxes and age
23.
by dbmikus 2mo ago
I'm working on https://www.amika.dev/ , which lets you put sandboxed agents on cloud VMs and then message them over the internet. It's for agent + human devboxes, for chatting with coding agents from the web, or au
24.
Axioms for a new operating system for AI agents(fixpoint.co)
3 points by dbmikus 2mo ago|0 comments
25.
by dbmikus 2mo ago
time to bring back the dev email distribution list
26.
by dbmikus 2mo ago
Nope, but I thought about moving hosting (or to Forgejo) because of (a) GitHub's issues, and (b) I like the idea of using an OSS code forge I suppose since Codeberg is a totally free non-profit for OSS projects, it makes it more reason
27.
by dbmikus 2mo ago
Identity is more than a name. It is also proving that you own that identity (aka authentication)
28.
by dbmikus 2mo ago
But the identity part of git is not (unless you count pgp signing of each commit, which never took off at a large scale) and the git tools don't automatically propagate repo changes by default across a network
29.
by dbmikus 2mo ago
Well, definitely makes me inclined to never use Codeberg for source hosting if they can just get together and decide to ban an entire category of source repo. It makes Codeberg seem like an unserious project.
30.
by dbmikus 3mo ago
Really freaky seeing how many of these are bedrooms.

More ›