Would also be interested in examples of a CLAUDE.md file that works well in Claude, but works poorly with Codex.
732 karma · joined July 30, 2015
YC S22 + F25 alum
email me: dylan+hn [at] amika.dev
[ my public key: https://keybase.io/dbmikus; my proof: https://keybase.io/dbmikus/sigs/hKAT57HrL4WNrtLuYDHaD10eRu99ZJiCylweoAKoGx4 ]
YC Badge: 0x00c0b5e3efeab93cdadd4b5136d53985e6dd303f
Would also be interested in examples of a CLAUDE.md file that works well in Claude, but works poorly with Codex.
Regarding security, I think you need three things:
1. You need the agent to run inside a sandbox.
2. You need a safe perimeter or proxy that can apply deterministic filtering rules on what makes it into the AI agent's sandbox and the HTTP requests and responses that agent sends out from the sandbox.
3. The bot should have its own email accounts, or maybe be configured to only send/read from certain email addresses
I'm working on a product that makes it as easy to spin up remote agent sandboxes as it is to git push and git pull. Then when we get that working well we're putting a proxy around each sandbox to let users control filtering rules.I personally see a future where there are many different types of *Claws, coding agents, etc. and I think they need a new "operating system", so to speak.
Self-plug at the end: https://github.com/gofixpoint/amika. The OSS part of my startup, focused on sandbox coding agents right now :)
PS: I enjoyed the entropytown.com blog! bookmarking it
It sounds like a big part of your use case is to safely give an agent control of your computer? Like, for things besides codegen?
We're probably not going to directly support that type of use case, since we're focused on code-gen agents and migrating their work between localhost and the cloud.
We are going to add dynamic filesystem mounting, for after sandbox creation. Haven't figured out the exact implementation yet. Might be a FUSE layer we build ourselves. Mutagen is pretty interesting as well here.
How does this compare with Codex's and Claude's built-in sandboxing?
It's tailored to play nicely with Git: spin up sandboxes form CLI, expose TCP/UDP ports of apps to check your work, and if running hosted sandboxes, share the sandbox URLs with teammates. I basically want running sandboxed agents to be as easy as `git clone ...`.
Docs are early and edges are rough. This week I'm starting to dogfood all my dev using Amika. Feedback is super appreciated!
FYI: we are also a startup, but local sandbox mgmt will stay OSS.
It's this.
Don't have a Dropbox moment ;) [1]
And totally agree that instead of reinventing the wheel here, we should just lift from how operating systems work, for two reasons:
1. there's a bunch of work and proven systems there already
2. it uses tools that exist in training data, instead of net new tools
If no one is marketing a product, then nobody knows about it.
I've been curious how much these AI models look for more niche coding language expertise, and what other knowledge frontiers they're focusing on (like law, medical, finance, etc.)
It has some Obsidian-like features inside Org Mode.
So, if you're looking for an easier-to-use UI, it's not it, but if you're looking for Obsidian-like linking and backlinking, it has that.
1. Agent can create its own tools and save them to memory
2. You create a SQL (and web app?) workbench per agent run
3. Grok fell off a cliff in the last month. Was this consistent over multiple runs?
4. Agents have a difficult time backtracking. Would unwinding system state and agent context make backtracking better? (Harder to implement this, though)
5. Since each new month only uses final state from previous month, agent has no way to understand why error occurred in previous month
Cool experiment! Was it difficult building the observable SQL workbench? And how many humans-in-the-loop did you have?I'm super interested in learning more about the training process of world and robotics model and the data challenges there.
Obviously since this is open source, then I can self host it. What other reasons?
Just curious!
https://www.reuters.com/world/us/us-judge-extends-block-trum...
The Lindy Effect for software: the longer software appears to be bug-free, the more likely it is bug-free.
I think there is room for statistical AI to operate symbolic systems so we can better control outputs. Actually, that's kind of what is going on when we ask AI to write code.
That said, we can still isolate and modify parts of a network, and combine models trained for different tasks. But you need to break things down into components after the fact, instead of beforehand, in order to get the benefits of learning via scale of data + compute.
[1]: http://www.incompleteideas.net/IncIdeas/BitterLesson.html
We have users with very similar use cases to yours. Want to email me? dylan@fixpoint.co. I'm one of the founders :)
Do you have any restrictions on sites we can scrape? I am likely going to do some public LinkedIn scraping (logged out, legally compliant).