I'm an physician who previously had wrist tendinosis and carpal tunnel and made the keyboard for myself. I'm trying to get the keyboard registered as a medical device for treatment of hand/wrist repetitive strain injury. Currently getting design for manufacturing finalized, and waiting on injection mold prototypes. Hoping to launch on Kickstarter in the next few months.
Also concurrently waiting on ethics approval for a clinical study, which will happen after launch. We had quite promising results from user testing, so I'm cautiously optimistic about the study.
For a competitive split concave keyboard, see Kinesis Advantage 360 keyboards at https://kinesis-ergo.com.
(I use the Advantage II with a trackpad in the middle (i.e., the split would be a problem ergonomically because it forces more movement to use the mouse).)
Oh shoot thanks for letting me know! I just pushed that update this weekend. I'll auto-confirm anyone who signs up until I fix it later tonight. I've put you on the waitlist.
I'm making a concave split ergonomic keyboard that we plan to run a clinical trial on for hand/wrist RSI. Was originally planning on releasing it in Jan but it's getting delayed until sometime in March. Concurrently waiting on ethics board approval to run a preclinical trail for when it's ready.
I love frigate... just had my neighbors come by because their dog was sick and were wondering if the dog had got into something in our back yard. Pulled up frigate, searched for "black dog" on the backyard camera, and found all the video of their dog.
We’re still figuring things out in public, but a few key differences:
- Open-source from the start. Cua’s built under an MIT license with the goal of making Computer-Use agents easy and accessible to build. Cua's Lume CLI was our first step - we needed fast, reproducible VMs with near-native performance to even make this possible.
- Native macOS support. As far as we know, we’re the only ones offering macOS VMs out of the box, built specifically for Computer-Use workflows. And you can control them with a PyAutoGUI-compatible SDK (cua-computer) - so things like click, type, scroll just work, without needing to deal with any inter-process communication.
- Not just the computer/sandbox, but the agent too. We’re also shipping an Agent SDK (cua-agent) that helps you build and run these workflows without having to stitch everything together yourself. It works out of the box with OpenAI and Anthropic models, UI-Tars, and basically any VLM if you’re using the OmniParser agent loop.
- Not limited to Linux. The hosted version we’re working on won’t be Linux-only - we’re going to support macOS and Windows too.
What if it fails to mention a critically important piece of info? Would your company be liable or would I as a physician have be liable for its mistake?
Great question. Our software is designed to assist, not replace, the physician’s role in making clinical decisions. It accelerates the time between an inbound referral and patient care by extracting and organizing information, but the final review always remains with the physician.
To minimize risk, we implement safeguards to prevent hallucinations, and our system is built to flag potential missing or unclear information rather than override clinical judgment.
I'm an physician who previously had wrist tendinosis and carpal tunnel and made the keyboard for myself. I'm trying to get the keyboard registered as a medical device for treatment of hand/wrist repetitive strain injury. Currently getting design for manufacturing finalized, and waiting on injection mold prototypes. Hoping to launch on Kickstarter in the next few months.
Also concurrently waiting on ethics approval for a clinical study, which will happen after launch. We had quite promising results from user testing, so I'm cautiously optimistic about the study.
reply