Yeah we totally agree. That's why we work on the end-to-end app, not on a single prompt. You pick what parameters become knobs in the frontend. So if you have a giant app with 10 parameters (say 5 prompts, 5 numbers), great, wrap those and they become knobs on our frontend. We override during the actual end-to-end testing execution kinda like a Statsig / Launchdarkly (only with typing).
Awesome work Cai and Andy. Do you have advice on structuring functions for best results? (eg, is it a good idea to give my agent access to things like a calculator "in case it needs it" or be careful about spoon-feeding it the tools I think it needs)
Just tried it out in my dummy application, but it throws an error when you provide a suffix... which is officially supported by their documentation. Hoping they support this soon.
I understand the cartoony feedback. We're working on improving the quality of the avatars to be more adult / work focused. We do believe in avatars - they are one of the key points in our product - because we believe that being on video all day is soul crushing, but audio-only feels disconnected. The avatar provides privacy and personality at the same time. FWIW, you can turn on video if you want it too, we just default to the avatar.
Hey there - there is a search button that allows you to search messages. Is that not working for you? Reach out to us via the Pesto team chat in the app for support on this.
I am the author. FWIW I totally understand where you are coming from; I'm not happy with our explanation of "What is Pesto?". We will take our own pass on refining this, and I'd also appreciate if you tried it and gave me your thoughts on it. Right now "digital workplace" is the best we have.
The core concept is "rooms" - like Discord voice channels, only way more flexible and built for remote workers. They can be traditional video conferencing, lofi spaces for hanging out, or 2d spaces with spatial audio.
The goal is to give teams a flexible workplace consisting of a series of rooms purpose-built for their workflows.
We are focused on rooms, which are audio-first spaces, not text conversations like Slack. Rooms are flexible containers that can be as simple as a traditional video conference, or more sophisticated, eg walk around on a map or listen to lofi music.
You can't look at screen share without permission - this is clearly something we screwed up in the landing animation. It's supposed to show Katherine sharing her own screen.
Pricing is coming soon and will free tier + paid tier (think like Slack / Zoom pricing).
There are parallels to Discord; the HN audience knows Discord well and so if we were only trying to appeal to this audience we would probably market it that way. A large chunk (possibly the majority) of our existing users don't know about Discord though and it doesn't make sense to purely market it in relation to that.
There are also some noticeable differences, particularly:
- integrations are focused on work products, eg calendar, rather than what games you are playing etc
- rooms (similar to Discord voice channel) can be shared on a calendar for guests
- we prioritize different things in screenshare (quality over FPS, since it's for work not gaming)