hgaddipa001

5 ms·

1.
Benchmarking Slop, Introducing Slop Index (A Fun Slashy Research Project)(twitter.com)
2 points by hgaddipa001 3mo ago|0 comments
2.
by hgaddipa001 7mo ago
What results have you seen so far?
3.
Full secure meeting platform (Granola proof)
1 points by hgaddipa001 1y ago|0 comments
4.
by hgaddipa001 1y ago
Why wouldn't we be indexing at scale?
5.
by hgaddipa001 1y ago
Yep we're using Oauth, so it's easy for a user to disconnect.
6.
by hgaddipa001 1y ago
Fair enough makes sense to not have trust! We like to believe we're pretty trustworthy, and do our best to make everything secure.
7.
by hgaddipa001 1y ago
Thanks! Don't worry have worked with a few friends experienced in prompt injection to help with the platform. But will read these too :)
8.
by hgaddipa001 1y ago
We do a lot of processing on our backend to prevent against prompt injection, but there definitely still is some risk. We can do better on as is always the case. Need to read up on how CaMel does it. Do you have any good links?
9.
by hgaddipa001 1y ago
Hmm this is a good idea too
10.
by hgaddipa001 1y ago
Not sure we haven't ever done volume that size for one person, but in theory should be able too! We use indexing similar to glean (but a bit less elegant without the ACLs) Can talk more about your use case if you'd like to. Send m
11.
by hgaddipa001 1y ago
Unfortunately have an NDA with them so can't disclose (most of our providers are still in stealth)
12.
by hgaddipa001 1y ago
Hmm that's fair, we're definitely not the most exciting launch out there compared to others in our batch. I'd like to think the fact we do what we promise is exciting, but without trying the product hard to convey that well :
13.
by hgaddipa001 1y ago
Ohh we don't give it computer use access or anything like that. We inject tokens post tool call, so to protect users from the agent doing anything malicious.
14.
by hgaddipa001 1y ago
Why do you think privacy? Security I understand, but if you consent to giving it access would it not be fine for privacy.
15.
by hgaddipa001 1y ago
Hmm ig yeah I can be more granular. Yeah we store our user credentials on our side and manage them. Along with refreshing tokens and so forth
16.
by hgaddipa001 1y ago
Have you tried out Slashy? What makes you say that
17.
by hgaddipa001 1y ago
It's useful for quality. For example we can read and attach pdfs to gmail which not a lot of people can, since we have our own internal storage api.
18.
by hgaddipa001 1y ago
What would you like to see? Can tell you :)
19.
by hgaddipa001 1y ago
Runs on AWS for now!
20.
by hgaddipa001 1y ago
Oh I used Screen Studio :) Thanks for the compliment. Not worried about browser agents, as we actually have pretty deep integrations (we include semantic search as well as user action graphs). Naturally apis will always be better than brows
21.
by hgaddipa001 1y ago
We did a lot of internal testing but no official benchmark. We find that the less the agent knows, the more it hallucinates
22.
by hgaddipa001 1y ago
Yep! That's our goal long term to get better templates
23.
by hgaddipa001 1y ago
Smart
24.
by hgaddipa001 1y ago
ooh good idea!
25.
by hgaddipa001 1y ago
The agent does! We don't, and agent pulls in data only when executing queries
26.
by hgaddipa001 1y ago
It's a bit more complicated. We have a full custom single agent architecture, sort of like Manus that isn't fully compatible with MCP
27.
by hgaddipa001 1y ago
Unfortunately not able to get into their codebase
28.
by hgaddipa001 1y ago
We use Claude/OpenAI right now with Groq for tool routing! I'd say maybe to get comfortable try out the non email features first, but we don't have access to any of your data.
29.
by hgaddipa001 1y ago
Hmm we've been considering a chrome extension
30.
by hgaddipa001 1y ago
Find that the quality of them currently aren't there yet for a general system. They tend to be designed just to use that singular app instead of to be used in parallel with other apps.

More ›