Local voice and perception
Scope speech recognition, synthesis, and visual processing to local compute. Do not assume a device’s default services work without external connections.
Spatial computing.
Beside the work.
An agent should be able to meet you where you are. We explore how the same ongoing task could move from a screen into the space around you, with relevant context and explicit permission. These scenarios are research previews; hardware and sensing require validation.
Choose the interface.
Define its boundaries.
A local model alone is not enough. Voice, sensors, identity, and device services all need to fit the deployment boundary.
Local context and devices
Keep permitted environmental context and agent state inside the network. Validate device discovery, authentication, rendering, and communication dependencies.
Explicit human control
A gesture, voice, or familiar interface does not grant authority. Preserve review, stop, and recovery paths for consequential actions.
From the workstation to the lab bench.
One continuing piece of work.
Follow an illustrative lab briefing across a local workstation, a hands-busy voice interaction, and an authorized review. All participants and services stay within the facility network.
09:00
Set the direction.
Give the outcome to your team. They gather the context and divide the work.
Friday’s lab briefingILLUSTRATIVE EXPERIENCE
Shared workspace
You
Prepare Friday’s lab briefing. Bring together the research, the previous run, and the decisions we need to make.
Your agent
I’ll bring it together, prepare the recommendations, and propose time for your review.
Context connectedResearch startedReview planned
Same agents. Same context. A different way to connect.
Illustrative air-gapped lab workflow. Local services assumed; no microphone, location, or instrument access is used.Presence without
constant interruption.
These principles guide human interfaces built on Visca. Spatial and wearable concepts illustrate possible extensions; they are not required for the platform or a claim of released capabilities.
Context makes it relevant.
With context you choose to share, the experience can fit your surroundings, activity, and current project. At a bench, the protocol matters. Before a meeting, the decisions do.
Attention shapes the interface.
A spoken update when your hands are busy. A concise decision when you are moving. A shared workspace when the work needs your full attention.
Authority stays with you.
Moving to a new place never grants your agents new permission. You decide what they may access, what can happen automatically, and which actions need your judgment.
More than a working day.
At a laboratory bench, in a workshop, or making progress on a personal project, the connection fits the work you are doing.
Illustrative environmentTalk through the work. Inspect the result.
Build voice and visual experiences for research, code, and documents. Let people explain an outcome, inspect the evidence, and redirect the agent without losing the shared task.
“Prepare the meeting. Bring me the decisions.”Explore this world
One workplace across professional and personal pursuits. These scenarios illustrate the product vision; available integrations and physical capabilities depend on the deployment.
The interface appears
when you need it.
Agents keep the assignment moving within the authority you give them. You can ask what changed, redirect the work, or pause it without assembling the context again.
See the result and the evidence behind it.
Review consequential actions before they happen.
Decide which context you share and when.
Understand your controlRelevant context. Deliberate attention.
Whether you use Mellow or build a custom interface on Visca, decide what context is shared, when it is reliable, and how much attention an interaction deserves. Spatial patterns are illustrative extensions of that design.
Illustrative design scenario
An afternoon that changes around you
Suppose you leave your desk for a workshop while an agent prepares a project update. At the desk you can compare versions and inspect sources. At the bench your hands are busy; a short spoken answer about the current plan may be more useful. Later, on a shared train, the same update should not automatically become an audible announcement.
A place alone cannot resolve all of those choices. You may be visiting a lab rather than working on its experiment, or using a gym’s lobby for a call. The experience needs a way to accept your stated intent and correct a wrong assumption. Choosing a quiet mode or withholding location should remain a valid way to work.
The agent’s assignment continues through those changes. If it needs approval to share the update, the important content is stable: recipient, version, proposed action, and relevant caveat. The presentation can become more concise, but it cannot omit the information needed for an informed decision merely because the screen is small.
The target is continuity with less interruption: relevant information at the right moment, a clear correction when the context is wrong, and the same authority across every interface.
The cases worth designing for.
When context is uncertain
Prefer an explicit preference or a brief clarification over a confident assumption. A location hint should help select an interaction, not silently choose the project, disclose private content, or grant permission.
When the human is unavailable
Continue independent work within existing authority. Hold decisions that can wait, and make the reason visible on return. Urgency rules and alternate decision owners need deliberate setup; repeated notifications are not a substitute.
When a quieter interaction is insufficient
Offer a route to the full document or comparison. Some judgments deserve a larger view and focused attention. The best interface is the one that supports the decision, including a deliberate pause when the moment is wrong.
What to look for in an evaluation.
- Can you correct the inferred context without restarting the work?
- Does private information stay private when the surroundings change?
- Can you use the workplace effectively without sharing your location?
Agents keep working.
You keep living.
Use Mellow for a workspace that is already assembled, or bring your own application requirements to Visca.
Request a demo