You remember where the document is. It is on the office Mac, in the folder for the trip you planned last night. A friend asks about the arrangements while you are out. The useful answer needs one detail from that document and another from the conversation you have already had.
To you, this is one piece of life. To software, it can become several separate places: a file, a device, a message, a task. You end up carrying the connections yourself.
A personal assistant should help with those connections. That is the practical idea behind Zinley's work on continuity: one assistant that can keep the relevant context together and work in the places you explicitly allow.
Keep the responsibility together
Imagine asking Zinley to turn your trip plan into a packing list. This is an illustrative workflow, not a record of a completed customer task. The document is on your office Mac, but the responsibility is simple: read the approved plan, identify what you need, and prepare something useful.
Today's product centers on one Zinley with its own identity and the context you allow it to keep. When enabled, Zinley Computer handles supported work. Approved personal computers provide other places where the assistant can work with files and applications.
This lets a request be about the outcome you want. The device remains relevant because it determines where the information and capabilities are available. You should not have to describe a task as a sequence of machine names to explain why it matters.
The ambition is continuity at the level of your responsibility: the assistant understands what it has been asked to finish, even when the next useful step happens somewhere else.
A device connection is a real boundary
For the office Mac to participate, it must be online, running Zinley, signed in, and permitted for the task. A cloud computer cannot make a file on an offline device available. A remembered location does not create a connection.
That distinction deserves a clear place in the experience. If the document cannot be reached, the useful response is to explain what is missing and what can happen next. Guessing at its contents would make the task appear further along than it is.
The same is true of permissions. You can limit a task to one project and tell the assistant to leave other material alone. The work must also stay within the permissions available on that computer. A familiar assistant should respect those choices each time it works. Knowing that a file exists is different from being allowed to open it, and being allowed to read it is different from being allowed to send it to someone else.
Carry the context without carrying every detail everywhere
Continuity does not require every device or every person to receive everything your assistant knows. It requires the right context for the responsibility at hand.
A packing list may need the dates, the planned activities, and a few preferences you have shared. It does not need unrelated messages or the private details of another project. A conversation with a colleague may need an agreed update while leaving the background decision-making private.
This is why context, device access, and authority to act remain separate choices in our product direction. Each contributes something different. Personalization helps the assistant understand what is relevant. Access makes a resource available. Your instructions define the work it may do with that resource.
A lasting relationship with an assistant depends on keeping those distinctions understandable as the relationship grows.
Show what happened when work changes hands
A connection can succeed while a task fails. A file can be found while the requested edit is still unfinished. A message can be drafted and waiting for your decision. These are different outcomes, and they should stay different when the work returns to you.
Available history and receipts help you inspect the work. They provide a place to review the result, notice something missing, and give the next instruction. An unconfirmed result should remain unconfirmed.
Interruptions make this especially important. A computer can go offline, a request can change, or permission can be withdrawn while work is in progress. We continue studying how tasks should resume, how duplicate actions can be avoided, and how changed permissions should affect the remaining work. Those are problems to evaluate, not claims that every failure has been solved.
One assistant, with a longer horizon
This article began as broader research into networks of agents. Today's product direction is one personal assistant across approved devices. Household hardware, embedded systems, and universal device support remain separate research ambitions.
The near-term value is more concrete. You ask for help with something that matters to you. The assistant can use the supported tools and approved computers available for the task. It brings the work back with enough clarity for you to understand what happened and what still needs attention.
Over time, we want fewer useful intentions to get stranded between a phone, a computer, and a later moment that never arrives. Your day keeps moving. Your assistant should help the work move with it. See the current cross-device experience.