--- title: "Lukas (@flexchar) | Hashnode" description: "A developer you can trust. Read the latest articles by Lukas on Hashnode." url: "https://hashnode.com/@flexchar" --- @flexchar # Lukas @flexchar · Copenhagen, DK · Joined September 2023 A developer you can trust. ## Comments [You're right, it's two different things. The good thing about it is that I can approve via the pop up the access to a credential, unless it's one of the few limited for agents. What's the worst that could happen - well the exhaustion of approval prompts and getting to the muscle memory of approving. I have thought about different options. There are some very sophisticated write ups about the entire sandboxing and injecting secrets at the request level so the agent doesn't even know about it. My problem is how far I'm willing to trade the comfort away and how far I'm willing to trust it. Between being very secure with no comfort, and being very insecure with --dangerously-skip-permissions mode. Another problem is to maintain such a proxy/broker requires mental capacity on its own. That is already limited. So I stick with the compromise for now. Worth noting, this is why I don't let my agents read my email or install latest versions of the packages since that would complete the lethal trifecta thus taking me to the riskier area than I have the appetite for. I feel like the entire area is still very novel and I could probably write an entire piece on it. What have you done?](https://hashnode.com/posts/cowork-sandbox-claudecode-codex-laughing-at-it/6adb5a37699e191b20126ed8/comment/6adb77f269dcfbd64b3665a6#reply-6aecb992b45989dd6cd17e17) Reply · Article · Nov 5 · [Cowork Sandbox -> ClaudeCode & Codex Laughing at It](https://hashnode.com/posts/cowork-sandbox-claudecode-codex-laughing-at-it/6adb5a37699e191b20126ed8) [Yes, indeed... and I am torn between these options. I both realize very well the potential of the Lethal Trifecta that is possible and on the other hand, if i really want effective VA (virtual assistant), I am forced to make trade offs. So far I haven't gotten burned but I will also not let my agent read my emails before me nor do it on automated basis, so there is no easy prompt injection, furthermore, I do count on the auto mode and my operating guide to not allow any actions that actually submit data outside (sending emails, uploading files etc). But it is not ideal. I see Claude Code in Desktop introduced a new environments option so I will be checking that one up. But for short, my biggest deal breaker in Cowork was no way to let the agent access my 1password cli op.](https://hashnode.com/posts/cowork-sandbox-claudecode-codex-laughing-at-it/6adb5a37699e191b20126ed8/comment/6adb77f269dcfbd64b3665a6#reply-6adf1ad6ef751436395ce8ce) Reply · Article · Oct 26 · [Cowork Sandbox -> ClaudeCode & Codex Laughing at It](https://hashnode.com/posts/cowork-sandbox-claudecode-codex-laughing-at-it/6adb5a37699e191b20126ed8) [Hi Moisés, Sorry it took so long to respond! It is really specific to your project. The latency, if you use Cloudflare Workers for accessing the database, is very low. My problem was because I was using the SQL API from a separate application. That is why Turso local copies became so valuable. Furthermore, I didn't know when D1 will out of beta. I am happy with turso because there is no size limit, whereas D1 still has 10GB limit. My current database is already bigger than 10GB. Another point for me is that I don't want to be vendor locked in. The perception (which really may just be a trivial illusion) that I can download the sqlite file from Turso is what makes me believe that I could move out from Cloudflare in an hour - package my worker into a Bun.serve() docker container and deploy it on my server. I may never need to do that but who knows. I am a big fan of Cloudflare and I don't see them being bad in any way as long as it fits what you're doing. :) Hope that helps!](https://hashnode.com/posts/migrating-large-d1-to-turso/65d0689f4668b6f16155a217/comment/66538ca06181d7179b27a4e2#reply-6655e573f4ad55f498ad038e) Reply · Article · May 28, 2024 · [Migrating large D1 to Turso](https://hashnode.com/posts/migrating-large-d1-to-turso/65d0689f4668b6f16155a217) [Md Rakib Hossain Sounds like a very light project, you will do great no matter where but... I would totally stick with Turso. The latencies are marginal and you are getting a lot more for your bucks. A company doing one thing will always out do the one doing many things. Though the key reason for me is that fact that I am not vendor locked in. If you ever want to host at Vercel, Netlify or just spin up your own Docker container with Bun as a web server and drop it on the ridiculously cheap Hetzner VPS, you just do that. Where as with D1 you would be tied and have a work-demanding migration.](https://hashnode.com/posts/migrating-large-d1-to-turso/65d0689f4668b6f16155a217/comment/6635ca5ee9171aa406b40a83#reply-663886d42692e0f0c33327b7) Reply · Article · May 6, 2024 · [Migrating large D1 to Turso](https://hashnode.com/posts/migrating-large-d1-to-turso/65d0689f4668b6f16155a217) [Hey Rakib, actually none. I am really loving the embedded sync function. There is no native php driver for libsql(turso) so the fact that I can get sqlite file and use Laravel native methods made it a 100x deal. I did however hit a couple "issues" when I was optimizing indices where I caused a lot of GBs to be synced (around 50GBs over the billing period). I had a call with Gauba, founder of Turso, and he was very kind to waive it and further hear me how I am using it. I wouldn't call it a limitaion. Frankly, if it fits your use case, it's quite cheap. Although I have seen that Cloudflare finally introduced sqlite download support. What are you building if I may?](https://hashnode.com/posts/migrating-large-d1-to-turso/65d0689f4668b6f16155a217/comment/6635ca5ee9171aa406b40a83#reply-6637c154630cd4f2e1993b77) Reply · Article · May 5, 2024 · [Migrating large D1 to Turso](https://hashnode.com/posts/migrating-large-d1-to-turso/65d0689f4668b6f16155a217)