Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs

news.ycombinator.com

Post reply on HN
Print view View original

51–60 of 62 posts

Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs

#51

Post by motoxpro »

bfeynman wrote: post #31

kinda surprising to see basically just LLM wrappers still getting funded/interest. Neat idea obviously and nice to have, but that's sort of it. Fundamentally misses mark on what you can do already without AI (running tests on your actual doc code examples etc), and fact that any of the AI IDEs could turn part of this one with single switch to just append a doc friendly update to a commit. To think that soon we have a…

Ironically, the common (used to be common?) trope about foundation models being picks and shovels and LLM wrappers having no values is probably backwards. ChatGPT is the most valuable AI product and it's just a wrapper around an underlying LLM that is not 10x better than the rest of the models.

Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs

#52

Post by alach11 »

buss_jan wrote: post #50

Very real problem. We have started to worry about how to maintain the many cookbook samples and tutorials, we wrote/are planning on writing. Going over every user facing artefact after a code change is a non-starter, so you opt for versioning these things as they'll necessary become out of date. Very excited to give this a spin soon.

Even OpenAI's cookbook is out of date in many places. This is a really difficult and common problem!

Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs

#54

Post by prithvi2206 »

alach11 wrote: post #52
buss_jan wrote: post #50

Very real problem. We have started to worry about how to maintain the many cookbook samples and tutorials, we wrote/are planning on writing. Going over every user facing artefact after a code change is a non-starter, so you opt for versioning these things as they'll necessary become out of date. Very excited to give this a spin soon.

Even OpenAI's cookbook is out of date in many places. This is a really difficult and common problem!

Yeah, even with lots of full-time resources, companies' documentation regularly fall out of date. It's particularly ubiquitous in AI just because of how fast the general space is changing.

Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs

#56

Post by prithvi2206 »

prithvi2206 wrote: post #45
kylegalbraith wrote: post #41

This idea is cool and well-scoped to a specific pain point that can be solved today. This is something that I think we need more of when it comes to YC batches. However, you all should publish pricing before launching, and forcing me to book a call with you to use it is a nonstarter for me. I don't want to get tied to this tool and then be charged for it in some weird way; give me your v0 pricing so that I can pay fo…

Yeah, this is very valid. We opened up a self-service trial this week so that people can more easily give it a spin before deciding to join a paid plan, but we're still working on a lot of the customer experience things to offer a truly complete onboarding experience. Appreciate the feedback!

Forgot to post: link to try Promptless out right now is https://gopromptless.ai/hn

Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs

#57

Post by martypitt »

Looks great - well done!

Can you clarify the slack integration? I see you've mentioned it, but I'm unclear on the workflow.

A use-case I've thought about previously is support discussions we have on our slack channel, which indicate that we need to update our docs.

Is Promptless able to raise a PR with suggested updates on docs, based on question/answers in our support channels?

Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs

#58

Post by prithvi2206 »

martypitt wrote: post #57

Looks great - well done! Can you clarify the slack integration? I see you've mentioned it, but I'm unclear on the workflow. A use-case I've thought about previously is support discussions we have on our slack channel, which indicate that we need to update our docs. Is Promptless able to raise a PR with suggested updates on docs, based on question/answers in our support channels?

Happy to clarify! There are two main ways people are using the Slack integration: (1) You click the Promptless Slack message action (video below) on a thread that might warrant a doc update—Slack Connect channels are an extremely common use-case for this, and (2) You tag @Promptless in a DM or a channel with a brief instruction—people sometimes use this for simple requests, but after signing up for Promptless, you can also send Promptless a link to an old PR, and it'll use the Github API to read the content of the PR and draft an update.

Here's a video we made a month or so ago that shows how (1) works, hope that helps! https://www.tella.tv/video/cm5x8uj9f001d0al11vyxcnsc/view

Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs

#60

Post by bfeynman »

motoxpro wrote: post #51
bfeynman wrote: post #31

kinda surprising to see basically just LLM wrappers still getting funded/interest. Neat idea obviously and nice to have, but that's sort of it. Fundamentally misses mark on what you can do already without AI (running tests on your actual doc code examples etc), and fact that any of the AI IDEs could turn part of this one with single switch to just append a doc friendly update to a commit. To think that soon we have a…

Ironically, the common (used to be common?) trope about foundation models being picks and shovels and LLM wrappers having no values is probably backwards. ChatGPT is the most valuable AI product and it's just a wrapper around an underlying LLM that is not 10x better than the rest of the models.

I would not define ChatGPT as a wrapper, anything where you are doing actual training/learning and updating weights is by most persons definition, not a wrapper. Just injecting stuff into the context or using RAG is a wrapper because there are no weight updates anywhere.
Post reply on HN