A cloud workspace
A persistent environment for approved desktop tasks, designed to keep working while your own computer is off. Bring the applications, information, and context needed for the job.
Desktop agent · Coming soon
Step away. Your workspace stays with the task.
Our vision is a persistent cloud workspace where an agent can continue supported desktop tasks—even when your computer is off. Bring the tools, files, and instructions the work needs, and return to results you can inspect.
A dedicated cloud workspace
Work beyond the API.
An environment for desktop tasks, connected to your broader workflows.
A task with defined scope
The access you approve
A result you can inspect
Coming soon · Concept illustration, not a live product screen.
Why we are exploring it
Some work still happens on a screen.
APIs connect much of a business, but they do not cover every task. A process can still end at a portal, a legacy interface, or a file that needs to move between tools.
The desktop agent direction is about bringing that work into the same automation picture: a task with a defined scope, an environment to execute it, and a result that can connect back to your process.
This is a planned capability. The desktop agent is not available today, and we have not announced a release date.
The planned experience
A dedicated environment. A clear purpose.
Our direction is a cloud workspace configured for the work you approve, with access and context appropriate to the task.
Part of the workflow
Desktop work should connect with the rest of your process. We are exploring how tasks and their results fit alongside the workflows you build in ParsePilot.
Deliberate access
The intended model centers on the task and the access you approve. The specific controls and supported environments will be defined as the product develops.
Personalization, with your approval
Useful context should be a choice.
We are exploring optional preference learning so a workspace can reflect the ways you choose to work. That might mean an approved output format, a naming convention, or a recurring task preference.
The direction is to learn from context you approve. The exact behavior and controls are still being designed.
Illustrative preferences
Report format
Use the summary structure I approved.
File names
Follow our agreed naming convention.
Task boundaries
Use the information relevant to this task.
Where it could help
Start with the task, then define the environment.
These scenarios illustrate the direction we are exploring. They are not a list of supported desktop capabilities.
A recurring portal task
A process calls for information from a business portal with limited API access. A desktop task could handle the interface-based portion and pass the result back into the workflow.
A file handoff between systems
One tool produces a file that another process needs in a particular format or location. A scoped desktop task could help bridge that gap within a configured workspace.
A repeatable preparation step
Before a team member reviews an output, a sequence of familiar interface actions needs to happen. A desktop task could prepare the result for that person to inspect.
Available today / coming next
Build on the platform. Follow the desktop direction.
Platform today
Build document workflows with the visual builder and help from Otto. Configure supported integrations, run workflows, and inspect execution history and monitoring.
Desktop agent · Coming soon
See what you can build todayThe cloud desktop workspace and optional approved preference learning are planned. Continuous proactive AI analysis is also a roadmap direction, separate from today’s interactive Otto experience.
Good questions
What to know today.
Can I use the desktop agent now?
The desktop agent is coming soon. We have not announced a release date. Contact us to describe your use case or ask about the direction.
Will the workspace reproduce my entire computer?
The plan is a dedicated cloud workspace configured for approved tasks and context. Its supported applications, environments, and setup will be defined as the product develops.
Will preference learning be required?
The direction is optional preference learning using context you approve. The details of that experience and its controls are still being designed.
Is this the same as Otto?
Otto currently helps you build and understand workflows when you work with him. The desktop agent is a planned capability for performing desktop tasks in a cloud workspace.
What should I include when I contact you?
Describe the task, the applications or portals involved, the information it needs, and where a person should review the result. Please leave credentials and sensitive business data out of the message.
Help shape the direction
Tell us where your workflow still needs a desktop.
Share the task, the tools involved, and the outcome you need. Use our contact form to discuss your interest in the planned desktop agent.