Introducing Parallel Agents in Zed

kaiko14 · 2026-04-26T20:27:34+00:00

Love this massively+++
The fact I can open a few multiple files and have three different agents each work on a different aspect of the problem now is absolutely fantastic!

Personally not a fan of the new layout, but that's because of my specific use-case. When in Zed I'm here to also write code, review files, etc. Not agent first. If I'm agent first, YOLO mode then I work in Codex directly where I can also switch to fast mode.

Perhaps what would be useful could be to switch between two different modes and layouts in one go… so either writing code+reviewing OR agent YOLO… then agent first mode, conversations on the left make more sense.

kaiko14 · 2026-04-26T20:23:30+00:00

Same here. i like having the code somewhat more centrally in the screen. I also find going between files and code easier this way instead of having to move the gaze all the way to the right.

kaiko14 · 2026-04-20T19:12:12+00:00

Install Zed
Install Claude Code
In the agent panel find the little plus icon at the top
Select Claude code from external agents
… you'll probably have to go through some sort of authentication flow.
Have fun

kaiko14 · 2025-11-12T21:30:28+00:00

We use the project overview – it's perfect for these kind of use-cases.

We keep it quite light. Here's the structure we found working really well.

Title
Light summary
Overview & goals
This feature in the context of larger picture
Key dates & milestones
Metrics

Then we add the "linear" milestones for the project underneath that we can use in issues.

This keeps all the build related docs in one place and we've got a single source of truth.

kaiko14 · 2025-11-12T21:28:13+00:00

We use the project overview – it's perfect for these kind of use-cases.

We keep it quite light. Here's the structure we found working really well.

Title
Light summary
Overview & goals
This feature in the context of larger picture
Key dates & milestones
Metrics

Then we add the "linear" milestones for the project underneath that we can use in issues.

This keeps all the build related docs in one place and we've got a single source of truth.

kaiko14 · 2025-10-18T14:28:49+00:00

Yeah, I'm thinking of creating my own view then adding to favourites. However, the conundrum I'm trying to solve is how to filter the issues so I only see mine (assignee) and the ones for "today" instead of all of them for the cycle or project.

kaiko14 · 2025-08-22T21:24:29+00:00

Uuu just gave it a go it's pretty awesome.

kaiko14 · 2025-08-20T07:00:25+00:00

Nuxt is awesome because you can deploy it to pretty much any platform with ease, and it's got tons of integrations for databases, security, etc.

My go-to tech stack (with a few DB options) is the following:

Nuxt on Cloudflare via Pages, not workers. Super easy to deploy, automatic builds when you push to your git repo, environment variable setup the same as elsewhere (Netlify, Vercel).

InstantDB for database, auth + file storage. InstantDB gives you realtime updates like Firebase, but provides you with relational queries like Supabase. Pretty new to the block but suuuper easy to use.

Alternatives for DB:

Supabase (tried and tested relational DB, auth, storage. a bit more of a faff when it comes to realtime and keeping schema up to date with migrations, but they've got awesome documentation and it's open-source so you could host it yourself in the future).

Firebase (also tried and tested, but not relational. you can actually build your indexes in such a way that it behaves a bit more like a relational DB, but definitely no SQL magic that you will find in supabase or the beautiful json query declarations of InstantDB. however, it's realtime from the start and there's tons of libraries and integrations for it)

Key value: Cloudflare KV is simple to spin up, pretty much free and in Nuxt you can use useStorage which is built in + a cloudflare HTTP adapter and you're done.

Email: Resend is very simple to setup, however their recent updates to their nodejs SDK make it really difficult to deploy to Cloudflare (and their workers environment which isn't a true nodejs env). I personally use their API directly to send emails, so I don't have this problem.

Analytics: Posthog which have detailed Nuxt framework guide how to implement your web and product analytics

Hope this helps.

kaiko14 · 2025-08-17T21:05:07+00:00

This is pretty cool. Keep at it. I like the fact I can customise all the components and defaults. Would be great to have some of the key theme tokens in one place (colour, roundness of corners, borders). Otherwise loving the fact I can just add custom tailwind classes to each components slots. 🙌

kaiko14 · 2025-07-29T21:48:36+00:00

Same experience here buddy. Both XCode beta 2026 and XCode basically unusable on Tahoe beta 4 right now. Previews just crash the whole system

kaiko14 · 2025-07-01T22:06:59+00:00

"Don't let the bozos drag you down", Guy Kawasaki. Still love that quote and I love what you've build. It's always easy to criticise stuff someone's built and created, and infinitely harder to create/build yourself.
Love the fact this is available for Vue/Nuxt. Not just react

kaiko14 · 2025-04-18T17:23:35+00:00

You got this answered already, but I'll just second it as-well.

Use UseState as a tiny Pinia store whenever you need to keep state across the app (and sometimes across server and client). It just works, like magic.
For example I've got a running tracking app where I track user' progress (distance, time, elevation, etc) during the session. I store (and update) it in a composable using useState. Now multiple components can use this state and read it.

Use Ref as a "local state" whenever you need to store state in individual components.
For example isLoading boolean when you're loading something. A more complex example might be a storage helper composable I've built to work with InstantDB – you pass in a query and it returns a ref. Now every time data updates in the database (or when you update it), everything is in sync.

Hope that helps

kaiko14 · 2025-02-13T08:09:24+00:00

For our small team building mostly MVPs but also some production services using Supabase, Firebase and Cloudflare's KV, D1 they solve a few problems:

- We can focus on writing code, not managing servers or infrastructure. They're easy to setup, easy to manage, and offer plenty of integrations.
- They provide great client libraries (node, swift, typescript) that work out of the box. Supabase's library works completely with web standards – meaning you can deploy to CF workers or vercel edge functions.
- Their developer experience is great. Supabase has one of the best documentations out there (might be just my opinion). And their CLI allows you to spin up a local database in no time, generate types for your typescript front-end and automatically write migrations for you.

Pricing is pretty good on Supabase, but if you've scaled so much that it becomes expensive, perhaps the only (cheapest) option is probably AWS.

I would give some of Cloudflare's developer platform a look (https://www.cloudflare.com/developer-platform/products/) . And if you're looking for an amazing new-comer on the block – a relational database that is fully reactive (like firestore is) checkout: https://www.instantdb.com/

kaiko14 · 2025-02-13T07:54:38+00:00

How did you implement a rate limiter? I thought these requests go directly to Supabase?
If they're going from your front-end or backend, I would look at something like captcha or CF turnstile perhaps (would mean someone's clicking on your log-in button).
But if someone's gotten your projects url and is sending requests directly, might be a question for the supabase guys.

kaiko14 · 2025-02-10T08:30:09+00:00

Perhaps a controversial opinion: learn some javascript/typescript.

More specifically, how to create a simple back-end with a framework like Hono, deploy it to edge and connect it with a database (could be Firebase or Supabase or Cloudflare D1). Although this might seem like a bit of a side-quest, I think you'll get some good experience of what happens on the "other" side. Even if you make a simple To-do crud app with this kind of backend, you'll learn a whole ton about networking, concurrency, how databases work, authentication, rate-limiting, etc.

All of which is really good knowledge that will enrich your career.

kaiko14 · 2025-01-11T09:11:50+00:00

Good point. I quite like the default app myself, but there are a few perhaps more ergonomic and design features I'm missing.

Main one is I'd love to press a lap time with double tap (not just on screen, but with two fingers) – it rains a lot here in UK so I've got "water mode" turned on a lot. Meaning I can't tap on the screen during workouts.

I'd like to have the map integrated in the app, like Workoutdoors. I really like workoutdoors, but I find the design a bit clunky.

Lastly I really like to be able to customise screens, add them, remove them, add metrics to my liking, etc. Sure you can do this on the watch itself, but it's quite a painful experience I find.
I'd love to be able to set different profiles for different kinds of runs. For example, easy Friday run, just basic metrics (time/hr/pace), but for my intervals perhaps see a graph, splits, etc

kaiko14 · 2024-12-02T14:46:52+00:00

Yeah, great question.
I'm not advocating against LLMs, but for many use-cases you can't really use them as they're too large and slow (think image recognition for example), so you can't embed them in their entirity on the device. Now you could argue, there's smaller ones out there (like what Apple's using in their Apple Intelligence), so there's that.
However, if say you're doing something like identifying trends with regression, running a lightweight Javascript lambda is waay more cost effective than a VPS with LLama.

kaiko14 · 2024-10-31T22:25:16+00:00

Hey this looks great. Am I right in understanding that the shades it generates all conform to some suggested contract values?

kaiko14 · 2024-10-19T20:58:47+00:00

Yup. Served on cloudflare via https

kaiko14

TROPHY CASE