Recent submissions

Comment · 26 days ago
The fact that Deno development is being suspended doesn't mean the community can't step in. The Deno runtime is licensed under MIT. Such forks might be impulse to grow even further.
Comment · 1 month ago
Looks great, and something I might try for my project. I am currently at stage of single mailbox, and bunch automation around it.

For example, Google Apps Script trigger Claude Code routine to investigate issue, and draft email ahead of me looking at it. If I do not like draft, I get back to Claude session to fix draft, and make PR to fix prompt for next time.

Curious, why did you choose OpenAI over CloudFlare AI (harness etc.)?

Comment · 2 months ago
They do not export devices, they export services.
Comment · 4 months ago
Comment · 6 months ago
I'm a Claude Code Web fan and a rather heavy user. So I was interested in your product. However, I couldn't find an answer on the website. What parts did you find so good that you ported them?
Comment · 6 months ago
Comment · 6 months ago
Comment · 7 months ago
If the problem is excessive deployments via GitHub Actions, why not use concurrency control on GitHub Actions ( https://docs.github.com/en/actions/how-tos/write-workflows/c... ) instead of relying on agent randomness and the hope that it won't make the same mistake again? Am I missing something?
Comment · 7 months ago
Of course, this scheduled can be implemented on top of existing tools. However, it's incredibly convenient to have a UI where:

- you can easily edit the prompt

- you can see the prompt execution history

- you don't need any infrastructure to orchestrate it

- it works even when your computer is off

Once you start using it, it turns out to be very convenient.

Comment · 7 months ago
That feature was silent launched about week ago for me.

I use it to:

- perform review of latest changes of code to update my documentation (security policies, user documentation etc.)

- perform review to latest changes of code, triage them, deduplicate and improve code - I review them, close them with comments for over-engoneering / add review for auto-fix

- perform review of open GitHub issue with label, select the one with highest impact, comment with rationale, implement it and make pull request - I wake up and I have a few pull request to fix issues that I can approve /finish in existing Claude Code thread

I want also use it to: - review recent Sentry issues, make GitHub issues for the one with highest priority, make pull request with proposed fix - I can just wake up and see that some crash is ready to be resolved

Limit of 3 scheduled jobs is pretty impactful, but playing with it give me a nice idea on how I can reduce my manual work.

Comment · 7 months ago
CloudFlare for their serverless offering did it, and it works decent.
Comment · 8 months ago
How are you performing backup of FerratDB? Are you using MongoDB tools, or are you using PostgreSQL-specific tools?
Comment · 8 months ago
Nowadays universal answer for "what? why?" is AI. AI agent needs VMs to run generated code in sandbox as they can not be trusted.
Comment · 9 months ago
You can install VSCode extension and use "/ide" to connect them.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton