baileywickham

5 ms·

1. 1.▲
   Show HN: Jixp, a Lisp DSL for describing Jax neural nets(github.com)

   6 points by baileywickham 2mo ago|0 comments
2. 2.▲
   by baileywickham 6mo ago

   Thanks for the feedback here, this matches a bunch of patterns we have seen. One of the fundamental problems is OpenClaw is tech for nerds. It's hard to use, it breaks all the time, it's built on LLMs, etc. We'd like to be th
3. 3.▲
   by baileywickham 6mo ago

   Go for it!
4. 4.▲
   by baileywickham 6mo ago

   I think I agree here but for us it's more of a defense in depth thing. If you want to give it access to your email you are opening yourself up to attacks, but it doesn't have that access by default. We have an integration to give
5. 5.▲
   by baileywickham 6mo ago

   Claude Code is awesome, I use it all day, every day. OpenClaw is similar but not the same. I think if all you do is write code, CC is probably best for you. OpenClaw is interesting because it does a lot of things ok, but it was the first to
6. 6.▲
   by baileywickham 6mo ago

   OpenClaw doesn't play well with SDKs like that. It expects to be able to run on a full machine (or container), to execute commands, to write files to disk. If we wanted we could fork and run something like this but we want to stay as c
7. 7.▲
   by baileywickham 6mo ago

   You're right that security is a major risk. Our perspective here is that by defaulting to an EC2 instance, you're in control of what data is at risk. If you connect Google Workspace, you are exposing yourself to some security risk
8. 8.▲
   by baileywickham 6mo ago

   It's an Amazon Linux image on an EC2 instance. We install some custom packages too.
9. 9.▲
   by baileywickham 6mo ago

   We run a dedicated AI SRE for each instance with scoped creds for just their instance. OpenClaw by nature has security risks so we want to limit those as much as possible. We only provision integrations the user has explicitly configured.
10. 10.▲
    by baileywickham 6mo ago

    We allow you to backup to a private Github repo you own so if you want to version control your setup that way you can. Otherwise most changes are tracked in the chat history and the LLM has some ability to repair itself or validate changes