Skip to main content

Documentation Index

Fetch the complete documentation index at: https://agenticstudio.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Most recovery actions are available directly from Settings. Open that page first if the app is still accessible — it gives the fastest path to logs, backend restart, and backup export.

​
The app will not open

If Agentic Studio fails to launch or shows a startup error:
  1. Quit Agentic Studio completely (Cmd + Q or force quit from Activity Monitor)
  2. Reopen the app
  3. If it fails again, check whether macOS is blocking it — open System Settings → Privacy & Security and look for an Open Anyway prompt
  4. If there is no macOS block and the app still fails, continue to the logs section below

​
The app opens but the backend does not start

If the app window appears but the UI is not usable — blank state, spinner that never resolves, or an error about the backend:
  1. Open Settings from the bottom of the sidebar
  2. Use Open Logs to open the logs folder in Finder
  3. Look for recent error messages in the log files
  4. Try Restart Backend — this stops and restarts the local backend process without losing any data
  5. If the error persists after restart, note the error message from the logs before taking further steps

​
An agent run fails with “command not found”

This usually means the runtime’s CLI tool is not on the PATH that Agentic Studio uses when launching processes.
  1. Confirm the CLI is installed: open Terminal and run the command directly (e.g., claude, codex, gemini)
  2. If it works in Terminal but not in Agentic Studio, the issue is PATH. macOS apps launched from the Dock or Finder do not inherit the shell PATH.
  3. Open Settings → find the agent in the heartbeat table → check the CLI path or Runtime path field
  4. Set the full absolute path to the binary (e.g., /usr/local/bin/claude or /Users/you/.nvm/versions/node/v20.0.0/bin/node)
  5. Retry the run from Inbox
To find the full path in Terminal: which claude (replace claude with the runtime command).

​
An agent is not waking up on schedule

  1. Open Settings
  2. Find the agent in the heartbeat table
  3. Check the Scheduler active column — if it shows inactive, the heartbeat is not running
  4. Check the Last heartbeat column — if it is stale by more than one interval, the agent missed its last cycle
  5. Try Restart Backend to reset the scheduler

​
Logs location

The logs folder is accessible from Settings → Open Logs. The path on disk is: 
~/.agenticstudio/instances/default/logs

​
Data and backup location

PathContents
~/.agenticstudio/instances/default/dataLocal database and app state
~/.agenticstudio/instances/default/data/backupsExported backup archives
Use Settings → Export Backup to create a backup before any destructive recovery steps.

​
Starting fresh

If local state is corrupted and recovery steps have not worked:
Reset Instance permanently deletes all local data — the database, run history, agent configuration, and logs. This cannot be undone. Export a backup first if there is any data worth preserving.
  1. Open Settings
  2. Use Export Backup to save a copy of the current state
  3. Use Reset Instance
  4. Complete onboarding again from the beginning
After a reset, previously configured agents, issues, and projects are gone. The backup export can be used to manually inspect the old database if needed, but it is not automatically restored.