NewSnippets: tell the AI about you and your company once.See how New modelClaude Sonnet 5.5 is now available.Read more
ON THE ROADMAP

For the system that will never get an API.

Every company has one: the licensing database, the customs portal, the ERP module whose vendor stopped answering years ago. We are building desktop control to operate that software the way a person does, on a machine you own and with consent. It is not available yet. Here is how it is designed to work, and what you can automate today.

Tell us you need it See integrations
How it is designed to work
Planned, not yet available
01
Record
Do the task once while the runner watches. It captures the steps, not a video.
02
Refine
Rename the steps, mark the inputs that change each time, delete the fumbles.
03
Check
Decide which steps a person has to confirm before the sequence runs unattended.
04
Run
On demand, on a schedule, or as one step inside a larger workflow.
The design

Automation for the last mile.

Desktop control is meant to be the option of last resort. When a connector exists, the connector is faster and far less brittle. These are the rules the runner is being built to follow.

For software with no API
The old ERP module, the desktop client with no integration, the portal that will never expose an endpoint. If a person can operate it, the runner should be able to.
Record once, replay
Walk through the task yourself while it records. Adjust the steps, name the inputs that change, then run it on demand or on a schedule.
On machines you own
The runner is designed to sit on your hardware or your VDI, inside your network. The desktop session would not be hosted by us.
Consent, visibly
A session should not start without consent on that machine, and should show a visible indicator while it runs. No invisible remote control.
The same guardrails
Screen contents read during a run go through the same sensitive info detection as anything typed into chat.
On the record
Which machine, which sequence, which steps. Recorded in the workspace alongside everything else, not in a separate tool.
AVAILABLE TODAY

Many systems without an API have a database.

Northwind's store system has no API, but its PostgreSQL database does not need one. Connect it once for the whole workspace, read only, and anyone can ask it questions in chat, like which customers ordered the most this quarter, or have a workflow report on it every Monday. CRMs and email sending connect the same way.

  • MySQL, MariaDB, PostgreSQL and SQL Server
  • Read only, read and write, or full access
  • An SSH bridge for databases behind a firewall
See workflows
WHAT WE ARE DESIGNING FOR
  • The runner on your machine, in your network, not a session we host
  • Consent on each machine, and an indicator while a session is active
  • Credentials from your own secret store, scoped to one sequence
  • Screen contents checked by the same guardrails as chat
Read the security page
Straight answers

What IT asks about desktop control.

Can we use desktop control today?

No. It is on the roadmap and not available in the app yet. If a system you depend on has no API, book a call and tell us which one. Real cases shape what we build first.

What can we automate today instead?

More than people expect. Many systems without an API still have a database underneath. Connect MySQL, MariaDB, PostgreSQL or SQL Server, read only if you prefer, through an SSH bridge if it sits behind a firewall, and let a scheduled workflow report on it. CRMs such as Pipedrive, ActiveCampaign and Brevo connect directly.

Will it be a remote-access tool?

No. The design is to run sequences you recorded, on machines that consented, with a visible indicator while a session is active. Nobody at StickyPrompts should be able to open a session on your machine.

What happens when the application changes its layout?

The sequence should stop rather than click the wrong thing, and tell its owner. Screen-driven automation is more brittle than an API, which is why we would rather it stop than improvise on a screen it no longer recognises.

Should we wait for this or use a connector?

Use a connector whenever one exists. It is faster, more reliable and easier to review. Desktop control is meant for the short, stubborn list of systems where no connector will ever exist.

On the roadmap

Tell us which legacy screen holds you up.

Desktop control is not available yet. Book a call and name the system you need it for. Real cases decide what we build first. In the meantime, connect the databases and CRMs that already have a way in.

Tell us you need it See integrations