Cool project!
Thanks! Still ironing out early kinks but I have a couple of friends using it. It’s been a joy to work on.
Readit Newsjsunderland323 commented on Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents · Posted by u/filipbalucha
jsunderland323 commented on Launch HN: Terminal Use (YC W26) – Vercel for filesystem-based agents · Posted by u/filipbalucha
This is really interesting, congrats on the launch.
The use case I’m trying to solve for is building a coding agent platform that reliably sets up our development stack well. Few questions!
In my case, I’m trying to build a one-shot coding agent platform that nicely spins up a docker-in-docker Supabase environment, runs a NextJS app, and durably listens to CI and iterates.
1) Can I use this with my ChatGPT pro or Claude max subscription? 2)
Hey I'm working on this problem (also a YC company but it's FOSS). It's a Dind approach https://coasts.dev/, I wonder if this works for your setup.
I don't think people are blasted for using AI (mostly), I think people are blasted for low effort work, just like pre-LLMs. LLMs just made it way easier to complete low effort projects, so therefore there is more of it.
Yeah, I agree but as someone in this thread said, if Temple OS came out today there is no way it wouldn’t be immediately derided as AI slop. That’s what worries me.
Blatant slop is obvious. Slop with a modicum of effort is harder. I’m still adjusting my slop-o-meter on other people’s work. It’s easy for me to identify my own slop, it’s not always so obvious when looking at someone else’s AI assisted work.
I’ve been mulling over this for a couple of days too. I have a project I want to share with the HN community that I put a substantial amount of effort into but it was definitely AI assisted (as is literally everything today).
I’ve read all of the source and I drove the architecture but it would be a stretch to say I didn’t ask for assistance on things that felt fuzzy or foreign to me. I also have generally stopped typing code. I still don’t think the LLM made the project though, it feels like my decision making.
If the bar for Show HN becomes no AI whatsoever then you’re just going to see a bunch of people covering their AI tracks. I’m reluctant to post it because I’m afraid of getting blasted by the community for using AI. At the same time, it is work that I’ve poured hundreds of hours into, that I’m proud of and that I think would be of interest to HN.
I read the Obliteratus post that made it to the front page the other day and I agree that is pure slop. While it’s frustrating that it took up front page space, it’s evident that the whole community caught on to the sloppiness of it all immediately and called it out. I just don’t think HN wants to set the precedent that no AI code should be shared.
I also saw a week or two ago that someone open sourced a project of theirs that wasn’t open source in the first place. The reason they stated was that they had vibe coded and were embarrassed to be discovered. If you want to get a concept out quickly with AI, you’re now hesitant to open source because of the precedent set by the community. I think that’s a scary thought to me. I would rather know the tools I’m using are AI generated/assisted and make the value judgement on if I trust the code and project owners.
jsunderland323 commented on You need to rewrite your CLI for AI agents justin.poehnelt.com/posts... · Posted by u/justinwp
I really like this - especially the embedded search. What do the embeddings and model cost you in terms of binary size ?
Umm it's not as bad I thought it would be. ~16mb per locale. ~28k words in the english docs.
Not schilling, just easier to show you the repo since it's open source. https://github.com/coast-guard/coasts
jsunderland323 commented on You need to rewrite your CLI for AI agents justin.poehnelt.com/posts... · Posted by u/justinwp
I'm working on a CLI now.
The pattern I used was this:
1) made a docs command that printed out the path of the available docs
$ my-cli docs
- README.md
- DOC1.md
- dir2/DOC2.md
2) added a --path flag to print out a specific doc (tried to keep each doc less than 400 lines).
$ my-cli docs --path dir2/DOC2.md
# Contents of DOC2.md
3) added embeddings so I could do semantic search
$ my-cli search "how do I install x?"
[1] DOC1.md
"You can install x by ..."
[2] dir2/DOC2.md
"after you install..."
You then just need a simple skill to tell the agent about the docs and search command.
I actually love this as a pattern, it works really well. I got it to work with i18n too.
jsunderland323 commented on Show HN: Guts – convert Golang types to TypeScript github.com/coder/guts... · Posted by u/emyrk
Type-first is cool. But I think I'll always aim to avoid gRPC, at least in part because grpc-web was so completely broken. I also have an instinctive aversion to binary formats. YMMV, just my PoV.
I’ve had a lot of success with grpc web. Had to patch a couple of things along the way. My biggest misgiving is thinking having bigints would be a good idea (it is not a good idea). Aside from that though, I’ve been happy with it. What felt broken to you?
When it comes to his Antichrist schtick I say "takes one to know one".
Also, Thiel seems like the sort of guy with the money and connections to pop the AI bubble whenever he believes it'd be advantageous, whether that is the product of a rational mind seems to be beside the point.
> seems like the sort of guy with the money and connections to pop the AI bubble
…and has been known to cause bank runs
jsunderland323 commented on Launch HN: JSX Tool (YC F25) – A Browser Dev-Panel IDE for React · Posted by u/jsunderland323
Most big corporates have their own inner sourced css components library. So when you get design feedback you wouldn't be directly editing the style in one self contained web application, which is what this demo is assuming.
We actually do support monorepos and it can do multi-file edits.
jsunderland323 commented on Launch HN: JSX Tool (YC F25) – A Browser Dev-Panel IDE for React · Posted by u/jsunderland323
I am failing to get it work on a "custom" setup. I run my own server with localhost pointed to the domain, with HTTPS on locally generated certificates.
I tried
npx @jsx-tool/jsx-tool start --logging --server-host codeinput.com --server-protocol https --server-port 443 --insecure
[jsx-tool] Proxy server running at http://localhost:4000
[jsx-tool] Forwarding to https://codeinput.com:443
[jsx-tool] WebSocket server listening on ws://localhost:12021
[jsx-tool] LSP worker exited with code 1
[jsx-tool] Restarting LSP worker...
[jsx-tool] LSP worker already started
(node:7881) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[jsx-tool] Proxy error: unable to verify the first certificate; if the root CA is installed locally, try running Node.js with --use-system-ca
[jsx-tool] Proxy error: unable to verify the first certificate; if the root CA is installed locally, try running Node.js with --use-system-ca
Hey csomar. If you switch over to discord I can work through it with you there.
> I understand you are trying to make a simple one click/command solution but some setups are more complicated than the standard yarn dev nextjs app.
I agree our docs are totally lacking on the more advanced dns setups! I'm so sorry.
> Maybe you should explain a bit what the server does and what it needs to connect to? why does it need some kind of a "proxy"?
If you don't do the manual installation where you point to the web-socket server in your <head>, it will inject that tag into your <head> tag. The web socket it how the chrome extension communicates with your file system.
You don't need the proxy for most things. It's fine to continue to just use codeinput.com as long as you have a way of making the websocket url discoverable to the extension.
The only other use case for the proxy is if you are on a page that has over 10k react fibers and are not using vite. This comes up a lot in things like CRMs or Next projects with a lot of 3rd party dependencies. In that case we have to find and replace a part of the react source that limits the number of React Fibers with source maps from 10k to 1m.
I tried to give a system design overview here but I will be the first to admit that it's pretty lacking https://jsxtool.com/docs/dev-server/system-design