# Maintenance and reference

Update AppJuice, locate app data, and troubleshoot common problems.

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

## Update AppJuice

Use Check for Updates in the AppJuice menu. Review the changes and follow the download and installation prompts. The update view can show the releases between your installed version and the latest available version.

You can also browse [Release notes](https://appjuice.app/guide/releases/). If the update view reports incomplete history, use that page to check earlier changes. Save work and allow active tasks to finish before restarting for an update.

## Troubleshoot a task

No model or capability available: Open AI Services, test the required connection, then inspect AI Capabilities. A working Agent model does not enable every image or speech operation.
A task fails or stops responding: Inspect the latest activity and error. Check provider availability and use Stop if needed. Review partial results before repeating actions.
An action is denied: Read the requested path and the review reason. Check [Files and permissions](https://appjuice.app/guide/permissions/) before changing access.
A file has no supported preview: Use an available download or open action and inspect it in an appropriate application.
An app does not behave as expected: Open Tweak, describe the exact steps and result, and ask Builder to investigate. Include the error text where available.
A remote app is unavailable: Check that the host and app are running, that the address is reachable, and that the browser is approved.

## Locate and back up data

For standard installations, AppJuice stores its files under these locations. A custom installation can use a different storage root.

- macOS: `~/Library/Application Support/AppJuice`
- Windows: `%APPDATA%\AppJuice`
- Linux: `~/.local/share/appjuice`

App workspaces are under the `apps` folder. Stop the app before copying live data files for backup. Keep both the app source and the data needed for its workflow. Databases and external services may need their own backup method.

App exports intentionally omit private runtime data. Source Snapshots do not replace data backups. Encrypted credentials can depend on the original machine's secure storage; copying a directory alone may not make them usable on another machine.

## Inspect resource use and report a problem

Open System Monitor to inspect app and platform resource use. Stop unneeded work before restarting an app that is using unexpected resources.

When asking for help, include the AppJuice version, operating system, app name, steps to reproduce the problem, and the visible error. Remove credentials and private content from screenshots or logs. Community links are available from the [Juicery website](https://appjuice.app/juicery/).

## Advanced host operation

AppJuice can also run on a server. Use the package and instructions for the supported platform. Command-line users can inspect the installed CLI with `appjuice --help`.

For a container deployment, explicitly configure persistent storage and mounted folders. File actions operate on that server's available storage. Desktop-only functions require an appropriate host and may not be present. Keep remote access and app permissions configured for the deployment.

## Terms used in this guide

Brew: The conversation used to plan a new app.
Builder: The coding assistant that creates or changes an app.
Use / Tweak: Use operates the app; Tweak changes how it works.
Runtime Agent: An assistant that performs user tasks inside an app.
Session: A saved Agent conversation.
Artifact: A file published as a conversation result.
Provider / model: A connected AI service and a model available through it.
Skill / tool: A Skill gives instructions; a tool performs an operation.
API / helper: An interface app code uses to request a platform capability. Builder can add these calls for you.

Keyboard shortcuts are shown in app menus and tooltips. Their availability depends on the current view and operating system.