> ## Documentation Index
> Fetch the complete documentation index at: https://docs.archetype.ing/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> What to do when the app or CLI cannot reach its host, a sign-in expired, an MCP server fails, a plugin is off or notifications do not come.

Start here:

```bash theme={null}
archetype --doctor          # config, model, keys and records, without calling a model
archetype daemon status     # whether the background service runs, for each folder
archetype --version
```

## The app cannot reach its host

The desktop app runs its own host. If the host stops after it was ready, the app restarts it, up to three times in five minutes. If it stops while starting, the app says why, with **Try Again** and **Show Log**.

* Restart it by hand with **File → Restart Archetype**.
* If the app says **The host started again. Open Archetype again to reconnect.**, close and open the app.
* **A host on a server:** the app connects with your system's `ssh`, which must work from a terminal without a password prompt. Use **Reconnect** (in **File**, or **Manage → Settings → Servers**). An older server is offered **Update and Reconnect**. If it still cannot connect, **Use This Computer** opens the local host instead.
* **A phone:** if it says **Could not reach** your computer, check the computer is on and the app or its host runs there. If Archetype says a port is taken, set `phones.port` in the config file to another. See [Devices](https://docs.archetype.ing/en/use/devices.md).

## Chats, schedules or triggers get no answer

These run in the background service, also with the app closed.

```bash theme={null}
archetype daemon status                # exits 0 only while it runs
archetype daemon logs -n 100 --follow  # its log
archetype daemon restart               # start it again with the config as it is now
archetype daemon install               # install it again if it is missing
```

If the app says **The background service is installed but not running, so chats go unanswered.**, press **Restart it**.

The service does not get your shell's environment. Put keys and tokens in `~/.config/archetype/env`, one `NAME=value` a line, readable only by you (`chmod 600`): the service refuses to start if others can read it.

## A sign-in expired

| Where | What you see | What to do |
| - | - | - |
| A model or engine | **The sign-in expired. Sign in again.** | Sign in again where it says. See [Engines](https://docs.archetype.ing/en/use/engines.md). |
| A team | **Sign in to … to open it** | Sign in to the company from the sidebar. |
| An app (Gmail, Notion, Linear…) | **Connect again** | **Manage → Connections → Apps**, then connect it again. |
| A messenger account | **Reconnect** | Press it on that account. See [Accounts](https://docs.archetype.ing/en/use/accounts.md). |

## An MCP server fails

```bash theme={null}
archetype mcp list          # the servers, and the plugins' own
archetype mcp check NAME    # start it and list its tools
archetype mcp login NAME    # sign in, for a server that asks
```

A server that cannot be reached on a turn is left out of that turn, and the rest go on. A server with `"disabled": true` does not run. See [MCP servers](https://docs.archetype.ing/en/extend/mcp.md).

## A plugin is off or missing

* Check **Manage → Plugins**. **Drafts** and **Meals** are off until you turn them on.
* A plugin turned off in `~/.config/archetype/config.json` (`"plugins": { "name": false }`) stays off.
* On a company's host, an admin chooses which roles see a plugin and get its tools. If yours does not, ask an admin. See [Hosting a company](https://docs.archetype.ing/en/teams/hosting.md).
* **Music** works on a Mac only, and needs macOS to allow Archetype to control the app. See [Music](https://docs.archetype.ing/en/plugins/music.md).

## Notifications do not come

* Open **Manage → My settings → Notification settings**. Each device says whether it gets them: **Off in the system's settings**, **Off in this browser**, **Blocked by this browser** or **Not reachable** say why not.
* Turn them on in the system's settings for Archetype, then check again.
* **Quiet hours** hold notices back, and **Muted sessions** get none.
* A notice is not shown while its conversation is on screen in a focused window.
* A team's mentions, replies and decisions follow that team's own preferences.

## Where the logs are

| What | Where |
| - | - |
| The desktop app's host | **Help → Show Log**, or **Help → Show Logs Folder** |
| The background service | `archetype daemon logs`, or `daemon/daemon.log` in the folder's records |
| A company's host you run | `docker compose logs -f archetype` |

Logs leave out access tokens. Look over a log for anything private before you send it.

## Report a problem

Email [help@archetype.ing](mailto:help@archetype.ing) with:

* what you did, what you expected and what happened;
* the computer and system, and `archetype --version`;
* the output of `archetype --doctor`, and the lines of the log around the problem;
* for a connected app or a plugin, its name.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.