Desktop Companion and Device Pairing

The MarkDocket Desktop companion is a native application that pairs with your web account and runs supervised USPTO form-filling workflows in your own Chrome browser. Because filings are executed locally — not through MarkDocket's servers — you maintain full control over credentials and submission timing.

How pairing works

Pairing connects the Desktop app to your MarkDocket account using a short-lived one-time code. Once paired, the Desktop app receives a device token it uses to poll for filing jobs. Your session cookies and web credentials are never sent to the Desktop app directly.

Pair a new device

1. Open the Desktop companion app on your Mac or Windows computer.
2. In the web app, go to Settings → Devices and click Pair new device.
3. A panel appears showing a one-time pairing code and a markdocket:// deep-link.
4. Either:
   • Click the deep-link (the Desktop app must already be running and listening), or
   • Manually enter the code displayed in the panel into the Desktop app's pairing screen.
5. The panel polls your device list automatically. When the Desktop app completes the handshake and your device count increases, the panel advances and confirms pairing — no manual refresh is needed.

Manage paired devices

All paired devices appear under Settings → Devices. You can revoke any device at any time — revoking a device token immediately prevents that device from receiving new filing jobs. Any job already in progress on that device will be marked as failed.

Supervised USPTO filing submissions

When you submit a trademark application draft for filing, MarkDocket queues a supervised filing job. The Desktop companion picks up the job, opens the USPTO electronic filing system in your local Chrome browser, fills in the application details, and waits for your confirmation before submitting.

This means:

• You are the submitter. The Desktop app fills forms on your behalf but does not click the final USPTO submission button without your involvement at key steps.
• Your USPTO credentials stay on your machine. The Desktop app uses the browser session and credentials already present in your Chrome profile.
• Screenshots are captured at each step and streamed back to the web app so you can follow progress in real time from any browser.

Starting a filing submission

1. Open a completed trademark draft and click Submit to USPTO.
2. MarkDocket validates the draft and queues a filing job. The job enters the queued state immediately.
3. Ensure the Desktop companion is running and paired. The app will pick up the job automatically.

Filing status states

Every filing submission moves through a defined set of states. You can monitor the current state — along with a live action log and screenshots — on the draft's Submission tab in the web app.

Handling awaiting_user pauses

When the workflow pauses at the awaiting_user state, the web app displays a Resume filing action alongside the most recent screenshot. This state occurs when USPTO requires a manual step — for example, reviewing a fee summary, solving a challenge, or completing a CAPTCHA.

To continue:

1. Switch to the Chrome window the Desktop companion opened.
2. Complete the required step manually.
3. Return to the web app and click Resume filing, or complete the action directly in Chrome — the Desktop companion detects your interaction and advances automatically.

Handling awaiting_login

If the Desktop app reaches the USPTO login screen:

1. Sign in to your USPTO account in the Chrome window the Desktop companion opened.
2. Once logged in, the workflow resumes from awaiting_login back to running without any action in the web app.

Viewing submission history and screenshots

The Submission tab on any draft shows:

• The current state and a timestamped action log of every step the Desktop app completed.
• Screenshots captured at key moments, so you can verify what was entered and when.
• The USPTO confirmation number once the job reaches completed.

Screenshots and logs are stored in your MarkDocket vault and are available even after the Desktop companion has closed.

Desktop companion capabilities visible on OAuth consent

The Desktop companion uses device tokens, not OAuth access tokens. As a result, the Device pairing capability is explicitly excluded from MCP tokens — if you are building an integration using MarkDocket's hosted MCP or /v1/tools endpoints, those tokens cannot initiate or manage device pairings. Device pairing and filing submissions are only available through the web app and the Desktop companion itself.

Frequently asked questions

Can I have more than one device paired at a time? Yes. You can pair multiple Desktop companions — for example, a Mac and a Windows machine — and they all appear in Settings → Devices. Filing jobs are picked up by whichever companion is running and available.

Does the Desktop companion store my USPTO credentials? No. The Desktop companion uses the browser session already present in your local Chrome profile. It does not read, store, or transmit your USPTO username or password.

What happens if my internet connection drops mid-filing? The Desktop companion continues filling forms locally. If the connection is restored before the job times out, status updates and screenshots sync back to the web app. If the connection is not restored in time, the job transitions to failed and you can re-queue from the draft page.

Can I cancel a filing that is already running? Yes. Open the Submission tab on the draft and click Cancel filing. The Desktop companion will stop the workflow and the job transitions to cancelled. Note that any forms already submitted to the USPTO cannot be recalled through MarkDocket.