Excited to finally share what @DavoTheDev and I are building: @BernardLabsHQ (YC S26).
Running an appliance servicer takes relentless coordination. Owners, CSRs, dispatchers, technicians, and parts teams keep every job moving across calls, texts, warranty feeds, schedules, and systems that rarely talk to one another.
AI does not pull a washer out of a closet or carry a compressor up three flights. Technicians do.
Bernard gives servicers AI employees that work alongside their teams, taking on customer communication, scheduling, dispatch, diagnostic evidence collection, parts preparation, technician handoff, and follow-up.
At the center is Pre-ID, which helps technicians arrive with a likely diagnosis, ranked parts, supporting evidence, and a plan.
We are already working with some of the country’s largest servicers, helping their teams handle thousands of calls every day and get more repairs ready before the truck rolls.
Built for the people who keep the physical world running and make the first visit the last.
learn more at https://t.co/OrFYn7ZVth
@ericzakariasson Does this now work with multi repo set ups in the cloud? Or can I have isolated worktrees for multi repo set ups? I love cursor and the eyes in the code compared to Claude code but finding it hard to do multiple things in parallel given multi repo set ups and isolated testings
@cursor_ai is there a way I can auto-save built plan markdown files onto a linear ticket based off the linear provisioned git branch name? Would be so sweet to have and help evangelize engineering work done
@TheRohanVarma It would be hugely useful if ut could do tasks across repositories it has access too. Right now it only allows single repositories changes. But if I could make changes to my we app, mobile app, and api server in one go for a new feature that would be chefs kiss
@DataChaz@n8n_io How have you found the reliability of n8n? I see the huge functionality but in many cases I have run into real reliability issues with it (e.g. workspace down, cron jobs not firing, etc). How have you dealt with it?
@AWSSupport That’s the issue, is that your service health dashboard is not reflecting reality. It has been confirmed that Athena is having degradations from a bad deploy in us east 1