Remix.run Logo
▲ jonathanstrange 3 hours ago

Good to know how much you're "looking" closely after everything your customers are doing. The name of your company is in your profile, right?

▲lmf4lol 3 hours ago | parent [-]

Yes. We are Bluehouse. The homepage still sucks but we are working on a nice one right now without AI Slop :-)

▲yellow_lead 2 hours ago | parent [-]

Crazy to hear. So you look in user's sandboxes, does this comply with GDPR and other regulations?

▲timthelion 2 hours ago | parent | next [-]

Actually, for the purpose of providing the service its fine to look. They just aren't allowed to use what they see anywhere else. Just like your doctor hears about your health problems but can't sell your medical records. Whats with the nasty toxicity?

▲lmf4lol 2 hours ago | parent | prev | next [-]

We only look IF they ask us. Our users aren't engineers and often get stuck and even the LLM can't figure it out. Then - AND ONLY THEN - we jack into the sandbox and help them.

For instance, one customer has 15(!) cronjobs. And they all used LLM calls to do stuff. So they ran out of tokens super quick and asked us for help because they didn' tknow what to do. Its not an engineering company, the owner has a sales background. So we went in and wrote scripts for them so that the cron calls don't need to use the LLM anymore.

▲sksksk 2 hours ago | parent | next [-]

That’s interesting, so in that scenario, you fixed it for that customer.

How do you then ensure it’s fixed for customers in the future? Do you add instructions to agents to write scripts where possible?

▲lmf4lol 2 hours ago | parent [-]

Yes. Or we make a skill of it and offer it via our skills marketplace. Depends really on what the fix was. Sometimes its really a one-off issue, and sometimes it makes sense to roll the new "insights" out to everyone.

▲sksksk an hour ago | parent | next [-]

Thanks!

Another question I have, is from a product perspective, how do you decide how much of the internals you show to users (like token usage).

I always thought that seems like (from a non technical users POV), like a implementation detail; and quite hard to map to actual usage. For example, one request might use lots of tokens, and another will barely use any; but it can be difficult for a non technical user to undertand the difference.

▲lmf4lol an hour ago | parent [-]

intuition and a lot of talking with our customers :-)

▲newswasboring 43 minutes ago | parent | prev [-]

I am not a user of your service, but a "system diagnostics" skill is something I have been meaning to develop for my hermes instance. Things like checking if I have left any running servers, cleaning up consumed linux ISOs from jellyfin, check for any repeated tool failures etc. Also its fun to say "run system diagnostics".

▲customguy 38 minutes ago | parent | prev | next [-]

> For instance, one customer has 15(!) cronjobs.

But they didn't ask US for help. We didn't need to know a customer of yours is running 15 cronjobs. Even if this factoid itself may be harmless, it's a good thing to practice on how you talk about these things. I'm not saying you're doing anything wrong, I don't know that, but I totally get why how you talk about it rubs some people (including me) the wrong way.

> Its not an engineering company, the owner has a sales background.

Again, it's good if you have a close relationship with your customers, but we don't, and they don't have one with us.

▲lmf4lol 15 minutes ago | parent [-]

Thanks for the constructive feedback. I think you may be right about this. It thought it was anonymous enough in the way I phrased it. Just wanted to be honest.

▲m4rtink 2 hours ago | parent | prev [-]

Even just the possibility anyone other than the user can "take a look" makes a service like this unfit for purpose.

▲weird-eye-issue an hour ago | parent [-]

You do realize basically every service does this right?

▲m4rtink 43 minutes ago | parent [-]

Sure, which is why I think if one wants to run any agents with sensitive data, they need to be fully self hosted so that operators can't look into your data. Anything else is insane and will be used against you.

▲lmf4lol 14 minutes ago | parent | next [-]

Do you feel the same way about emails, cloud drives or SaaS like Salesforce or Jira?

▲weird-eye-issue 12 minutes ago | parent | prev [-]

> will be used against you

I mean I'm all for privacy and security but this statement right here just comes across as pretty paranoid

▲not-kinsale-joe 2 hours ago | parent | prev [-]

Can IT support in EU remote connect to view a users PC? or does that violate GDPR and other regulations?

▲baq 21 minutes ago | parent [-]

If the user agrees it’s fine, GDPR is really not the biggest concern in this case since the user should express consent anyway.