PUBLIC STATUS
Now
What we are working on, what we know, and what is still open.
Last updated:
Current focus
Current focus
Find out where software can take over setup, follow-through, and recovery without taking control away from the user.
Can you ask once, move on, and hear back only when you are needed?
We are finding where current tools do the job and where their setup, supervision, and handoffs still fall to the user.
If Capy cannot make that experience clearly better, it does not need to exist.
What we know
Early technical validation
Independent implementations coordinated reliably in controlled studies and recovered from the interruptions we tested.
We also have early evidence that continuity can survive changes in software and devices. The full user experience remains unproven.
Open questions
- Can the user hand off a task without having to supervise it?
- How much preparation does the product need to provide?
- Where are familiar tools already good enough?
- When does direct software coordination help?
- How little must separate implementations agree on?
- What belongs in Capy, and what belongs in products built on top?
Not happening now
There is no public beta, customer onboarding, hosted Capy network, token, reputation system, or payment product.
Capy is not being built to replace agents, messaging, email, Git, cloud providers, or operating systems.
About these updates
We update this page when the work or our conclusions change.
We share what helps people understand Capy. Private requests, individual scenarios, and implementation logs stay private.