Skip to content

The Agent-Human Interface Company

The developer platform for programmable agent-human interaction. A face on your screen. Context in your surroundings. New ways to express intent.

A face on your screen. Context in your surroundings. New ways to express intent.

An agent should be able to meet you where you are. Build across screens, spatial environments, and emerging human-signal interfaces with a shared foundation for input, context, tools, and permissions.

A product engineer reviewing a physical prototype at a sunlit studio desk

At work

Give your application a face and voice.

Explore conversations that connect people to the context and tools behind their work.
PEOPLE · AGENTS · INTERFACES01 / 08

Illustrative application areas · Interface and device availability varies.

Where developers build how
agents and humans interact.

From our in-house real-time avatar technology to spatial, neural, and subvocal interfaces.

Agents should change shape. Your context should stay yours.

Read the manifesto

The interaction layer

Start with the way
people interact.

A face when you want a conversation. A spatial interface when your surroundings matter. Supported silent input when speaking is inconvenient. Mellow’s SDKs and Visca’s shared foundation are how we are connecting these forms to continuing work. Explore each mode and its availability.

Visual presence

Give the conversation a face.

Design how an agent appears, responds, and shares visual context. Connect its presence to the same identity and work behind the conversation.

Explore face

More than an interface.
A foundation for real work.

A continuing agent needs identity, memory, knowledge, responsibilities, tools, and explicit permissions. These foundations give different interfaces a shared place to connect. Explore all 14 properties.

Know who you are interacting with.

Keep the same agent identity behind its face, voice, and workspace. Show its role and accountable human so recognition comes with an understandable scope.

IN THE BRIEFING EXAMPLE

The briefing has a responsible agent, from the first request to the finished result.

One identity. One shared context. One continuing piece of work.

Explore all 14 platform properties

One interaction.
Work that continues.

Explore how a conversation becomes agent activity, files, memory, and a decision. The work retains its context as people and agents contribute.

viscaAgent workspace Working together
One team.
One shared context.

Your team is on it.

One assignment. Everything connected.

Prepare Friday’s
partner briefing
Research checkedSources attached
Briefing draftedThree decisions, clearly laid out
Time reservedReady for your review
RWCResearch, writing, coordination.
The same piece of work.
Illustrative experience · Explore the workspace

BUILT ON VISCA

Meet Mellow.
Your workspace.
Your continuing agents.

Bring models, files, memory, tools, and decisions into a personal and development workspace. Visca is the platform. Mellow is the workspace and SDK family for building and experiencing new ways to interact.

Explore Mellow Free forever for personal use.
MELLOW / YOUR SIDE OF THE CONVERSATIONMellow waving hello
You stay in control.

Ask. Inspect. Decide.

Inside the platform

One platform.
Your application on top.

Behind every interface: execution, identity, memory, shared services, and context. Explore the stack that connects a human interaction to accountable agent work.

VISCA / SYSTEM ANATOMY
EXPLODED VIEW / 06 LAYERS

Direction · Judgment · Outcomes

Use Mellow. Or build your own.

Mellow is the workspace and SDK family built on Visca. Use the personal workspace or build a custom interface around shared context, tools, and permissions. Personal workspace use is free forever.

  • Natural direction
  • Clear review
  • Finished outcomes
ONE BRIEFING, THROUGH THE STACK

Review the briefing and decide what is ready to share.

Explore this layer

Conceptual product architecture. The plates visualize software layers, not physical hardware. Availability depends on the deployment.

Spatial computing.
Context beside the work.

Explore how voice, place, and shared context could support a researcher through a lab workflow. This interactive scenario is a research preview; device support varies.

09:00

Set the direction.

Give the outcome to your team. They gather the context and divide the work.

Friday’s lab briefing

ILLUSTRATIVE 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.

Human interaction.
Across the worlds you work in.

From an office conversation to a lab bench or a machine on site, the interface should fit the task. Explore the application areas we plan to serve.

A person working at a deskIllustrative environment

Talk 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.

Natural interaction.
Explicit authority.

Speaking, looking, or interacting with a device is not blanket consent. Define what an agent may access, which actions need review, and how a person can take over.

Choose a deployment that fits your data and environment. Air-gapped operation remains a deployment option requiring local models, services, and validated device dependencies.

Your authority stays yours

Ready when you are.

A clear decision, with the work behind it.

  • In our briefing example, the approved document will be shared with the internal research team. Internal notes stay private.

  • The example brings the intended recipient, final version, and supporting sources into view before sharing.

  • Approve the specific action, ask for a change, or hold it. Your location and activity do not grant extra permissions.

Illustrative review · No external action is taken

Where developers build how agents and humans interact.

Build on the Visca developer platform. Explore Mellow’s workspace and SDK family. The workspace is free forever for personal use.

Book a call