# Services and automation

Manage service credentials and add browser, desktop, or scheduled work to an app.

Source: https://appjuice.app/guide/services/
Updated: 2026-09-14
Guide baseline: AppJuice 0.350.4

## Store service credentials

Open Settings → Platform Vault to manage credentials used by app backends, such as a service API key. Vault values are encrypted locally and are not shown again as plain text in Settings.

When an app needs a service connection, follow its setup guidance and save the requested credential in the Vault. Do not paste secret values into Builder conversations. The app uses the saved credential to connect to the intended service.

## Choose the right settings section

AI Services: AI provider accounts, keys, gateways, and local model connections.
AI Capabilities: Available AI tasks and their model order.
Platform Vault: Credentials for services used by app backends.
Publishing: Connections used to publish eligible apps to Cloudflare or Railway.

## Repair a service connection

If an app reports missing or invalid credentials, check the named connection. Update the credential or sign in again using its settings. A connected service may also refuse a request because of its own permissions or limits.

Use Vault Reset only when the vault cannot be recovered through the normal flow. It replaces the vault's credentials and encryption key; read the confirmation and recovery information before proceeding.

## Browser and desktop work

Browser Use lets a suitably configured app interact with websites. Computer Use lets it interact with supported desktop interfaces. Tell Brew or Tweak what the app needs to do so it can add the appropriate workflow and tools.

These capabilities require their host tools and permissions. For example, macOS desktop control may need Accessibility and Screen Recording. They operate on the host running AppJuice, not automatically on a remote visitor's desktop.

A fixed sequence may be implemented directly in app code; an adaptive task can use a Runtime Agent. Website changes, sign-in requirements, or permissions can interrupt either kind of workflow.

## Run work on a schedule

Describe when the app should run and what it should do. Scheduled work is implemented by the app and usually does not need a platform-level switch.

Confirm the time zone, where results appear, what happens after a failure, and whether the app must remain running. Do not assume work will execute while its host is asleep or offline. The app's implementation determines missed-run and retry behavior.