Schedules, CLI, Mobile Companion, and privacy

© 2026 Quadropic Pvt Ltd. Proprietary and confidential. Use restrictions.

Scheduled Tasks#

Open Settings → Scheduled Tasks.

A schedule runs a saved prompt while Syntheo is open. It is a desktop automation, not a cloud job runner; a sleeping, closed, or offline desktop cannot execute it on time.

Choose a target#

Workspace: Runs one prompt in one directory. Use it for a focused recurring job.

Examples:

• review new changes for obvious regressions;
• refresh a generated report;
• run a narrow maintenance check;
• inspect dependency drift without applying updates.

Conductor: Runs an orchestration prompt across several directories. Use it when the scheduled outcome genuinely needs multi-workspace decomposition or several workers.

Examples:

• coordinate a weekly compatibility review across a client and API;
• collect release readiness evidence from several services;
• create separate audit tasks and one final synthesis.

Do not choose Conductor for a command one agent can run. Orchestration adds model calls and coordination state.

Create a schedule#

1. Choose New schedule.
2. Give it a descriptive name.
3. Choose Workspace or Conductor.
4. Select one or several directories.
5. Write the prompt.
6. Choose Daily, Weekdays, Weekly, or Custom.
7. Set the local time or a five-field cron expression.
8. Leave Enabled on and create it.

The schedule records its timezone. Verify that timezone after travel or system timezone changes.

Custom cron uses:

minute hour day-of-month month day-of-week

Examples:

0 9 * * 1-5     # weekdays at 09:00
30 17 * * 5     # Friday at 17:30
0 8 1 * *       # first day of each month at 08:00

Write automation-safe prompts#

An unattended prompt should bound mutation and failure:

Review changes since the previous run for clear correctness or security issues.
Do not edit, commit, push, install dependencies, or contact external services.
Create a concise findings task with severity, evidence, and suggested next step.
If there are no findings, report that explicitly.

For a mutating schedule:

Run the generated-client freshness check. If generated output is stale, update
only the generated directory and run its validator. Do not commit or push.
Stop without editing if dependency installation or a schema migration is needed.

Use Run now to test a new schedule while you are watching. Confirm:

• it opens the intended directory;
• the selected model assignments are available;
• permissions do not leave it permanently waiting;
• the result has a clear success/failure signal;
• repeated runs are idempotent or intentionally cumulative.

Pause rather than delete a schedule you may need again.

Command-line launcher#

Open Settings → About → Command Line and choose Install command.

If the app reports PATH setup needed, add the shown directory to PATH or restart the terminal. Then run:

syntheo <workspace-path> "prompt"

Examples:

syntheo . "fix the failing session tests and validate the focused suite"

syntheo ~/Developer/app "explain the release pipeline; do not edit" --action ask

syntheo . "plan the settings-store migration" \
  --action architect \
  --title "Settings migration plan" \
  --virtual-edit

Available options:

--action submit|ask|architect|debug
--title "Task title"
--virtual-edit
--no-focus

Use --no-focus from scripts or background terminal workflows so the desktop accepts the task without stealing focus.

The workspace path must be an existing directory. Relative paths resolve from the shell’s current directory, and ~ is expanded.

Shell quoting matters. Keep the prompt in one quoted argument. If the prompt contains substantial structured context, place that context in a workspace file and tell the task to read it.

Mobile Companion#

Open Settings → Mobile Companion. The companion can control tasks, approvals, terminal, and browser from an iPhone.

Pair on the same network#

1. Install/open the Syntheo mobile app.
2. Tap Connect with Desktop.
3. Choose Scan.
4. Scan the desktop QR and continue on the phone.

If scanning fails, expand Can’t scan? Enter the code by hand and enter the displayed address and rotating code.

The desktop shows connected and previously paired devices. Use Forget to revoke a device you no longer control. Use New code to rotate pairing details if the current code was exposed.

Connect from anywhere#

Expand Connect from anywhere and enter a trusted wss:// companion relay URL. The desktop opens an outbound TLS tunnel, so no router port forwarding is needed.

Important trust boundary:

• public relays must use WSS;
• the relay participates in the connection path and may be able to observe forwarded content;
• use the included self-hosted service or a relay operator you trust;
• turn remote access off when it is not needed.

Do not treat transport encryption to a relay as proof that the relay operator cannot inspect application traffic.

Mobile operating habits#

• Enable permission-needed sounds or mobile notifications for background agents.
• Verify task and directory before approving a tool remotely.
• Avoid approving commands whose full arguments are hard to inspect on a small screen.
• Give each person/device its own pairing and revoke lost devices immediately.
• Keep the desktop awake and Syntheo open for remote access.

Privacy Veil#

Privacy Veil keeps the app visible locally while hiding its window from supported screen recorders and meeting capture.

Enable it:

• in Settings → Theme & Display → Privacy Veil;
• with ⌘⇧V / Ctrl+Shift+V; or
• by long-pressing the top-bar Open control.

Choose whether it remains active until manually disabled or turns off after 15, 30, 60, or 120 minutes.

Use Privacy Veil when:

• screen sharing while private task content is open;
• recording another application;
• presenting with Syntheo in the background.

Do not rely on it to:

• redact notifications from other systems;
• remove secrets from stored threads;
• protect content from local users or malware;
• hide terminal commands copied into another visible app;
• replace access control.

Confirm your meeting or recording software respects the operating system’s capture exclusion before discussing sensitive material.

Background attention#

Open Settings → Audio to configure:

• task-completed sounds;
• permission-needed sounds;
• error sounds;
• volume;
• play only when Syntheo is unfocused.

The “unfocused only” option is useful when you run agents in the background but do not want sounds while actively watching the task.

System tray state also surfaces active agents and tasks that need input. A background workflow is only autonomous until it hits a permission or question that requires you.