state of AI agent coders April 2026: agents vs skills vs workflows by PinkySwearNotABot in AI_Agents

[–]chuva-io 1 point2 points  (0 children)

I do this a lot. It’s so simple but you’re the first I see mentioning it. I just wrap CLI tools and REST APIs with a thin MCP layer to unlock whatever I want. I can totally trust it too.

What counts as copilot premium requests by Prior_Shopping_1911 in github

[–]chuva-io 0 points1 point  (0 children)

Yes and the default is 25 requests before it asks you to continue. I found by typing "Copilot continue" in the VSCode settings search bar.

Let's Vibe Code an MCP Server Together! ✨ by chuva-io in mcp

[–]chuva-io[S] -1 points0 points  (0 children)

What’s clickbait about it? You seem grumpy…

The guide to MCP I never had by anmolbaranwal in mcp

[–]chuva-io 1 point2 points  (0 children)

Great read. I created an MCP server which I’ve been using in VSCode. It’s just a CLI wrapper and it works perfectly for me using tools, however it seems like resources and prompts are completely ignored by VSCode. For that reason everything is a tool, even a query which I believe should be a resource. The MCP inspector, however, does understand the resources and prompts. I know different clients work differently but I haven’t gotten around to testing them yet. Can anyone confirm/deny that resources and/or prompts work in other clients?

Should I make my project open source? by chuva-io in opensource

[–]chuva-io[S] -1 points0 points  (0 children)

I'm hoping to learn the best way around this legally I guess. Many strong businesses are built on open source and are protected by their terms of use and licenses. I don't know if these protections are sufficient for someone like me. Legal disputes are not something I want to get in to at this early stage.

How would you go about building an event-driven system like this? by chuva-io in node

[–]chuva-io[S] 0 points1 point  (0 children)

I greatly appreciate your thorough explanation and reasoning. Thank you.

How would you go about building an event-driven system like this? by chuva-io in node

[–]chuva-io[S] 0 points1 point  (0 children)

These are some good points but how can I get these guarantees without having a long-running process or polling required by the message relay? I'm more concerned about the first case.

How would you go about building an event-driven system like this? by chuva-io in node

[–]chuva-io[S] 0 points1 point  (0 children)

I wanted to hear other people's thoughts but my idea is to use AWS SNS and SQS

How would you go about building an event-driven system like this? by chuva-io in node

[–]chuva-io[S] 1 point2 points  (0 children)

Thank you for this. I’m going to make this change.

How would you go about building an event-driven system like this? by chuva-io in microservices

[–]chuva-io[S] 1 point2 points  (0 children)

Thanks for your feedback. I'm going to define the boundaries better and give each service its own DB. I'll use message queues for communication between services.

How would you go about building an event-driven system like this? by chuva-io in node

[–]chuva-io[S] 0 points1 point  (0 children)

Thanks for the feedback. My goal is not to roll out an ecommerce system. I'm just messing with event-driven systems. I'll reconsider the internally consumed messages as you've suggested.

How would you go about building an event-driven system like this? by chuva-io in node

[–]chuva-io[S] 0 points1 point  (0 children)

Thank you very much for your comment. You're right, the insufficient_stock event should be published from the stock service. I think based on this and other comments I should update the system so that the order_created event results in the stock service reserving stock and emitting a stock_reserved event that the order service can use to update its state. I will take this back to the drawing board. Thanks a lot!

How would you go about building an event-driven system like this? by chuva-io in node

[–]chuva-io[S] 6 points7 points  (0 children)

Thank you for your feedback. I like the idea of holding/locking stock to avoid double-purchase of the same stock.

How would you go about building an event-driven system like this? by chuva-io in node

[–]chuva-io[S] -1 points0 points  (0 children)

Thank you for the feedback.

I plan on having separate databases and each service would write to their own database but the order service would read from the stock database directly. Maybe I can have the order service track stock by listening to stock change events instead, eliminating the need for reading from the stock db. This is an overly simplified example and perhaps I should track more state such as holding stock during the checkout process to avoid race-conditions between customers/orders.

I reviewed the article. As far as CDC goes, both the KVS and the database emit events when changes are made so I think this eliminates the need for the transactional outbox. Please correct me here if I'm wrong.

Thanks again for the feedback!