FAQ

Yes. Each computer is an independent instance, with sessions and skills stored locally; memory doesn't sync between computers either ("Sync memory to the cloud" is only for Cloud Chat on your phone).

Yes. When you pick your computer in the mobile app, you see the same conversation as on the computer, which needs to stay online. When the computer is offline, you can keep talking in Cloud Chat, which can also search the web, read pictures you send, and generate images — but that is a separate conversation and won't appear on the computer.

Memory and settings must be migrated manually — see Backup, migration, and uninstall.

First check whether you're still in the same turn — skills take effect from the next one; then check it's toggled on in the Installed tab. The model decides on its own whether to call a skill; type / to call one yourself.

If the same version is already installed, it is reused rather than downloaded again; when a skill has a new version, installing it again downloads the new version and replaces the old one.

Grouped by collection under Added by me on the Installed tab, with anything outside a collection under Standalone skills; the fuller record lives in the install metadata inside the skill's directory.

Yes. Tell Cola what kind of skill you want and it will build it out with you.

Saying what to do and when is enough — Cola works out how to deliver the result. It only asks back in three cases: the result is meant to be sent out but the recipient is unclear; the task deletes things but doesn't say what; or it writes files outside the output folder but doesn't say where.

It depends on whether that alarm is set to skip or replay the most recent run — see the catch-up table in Smart Alarms. Don't assume every missed run is replayed.

Short results appear in the conversation. Generated files are saved in Cola's output folder: find them in the Outputs panel, or click a file name in the alarm's Run history to open it.

Yes. Pause, resume, delete, and edit from the page all reach Cola on the next turn; they just aren't rendered as chat bubbles.

Yes — create it with one sentence in the conversation. Schedules like this show only as a text description in the schedule control and can't be edited there; to change one, say so in the conversation.

Imprints are written only after a moment with real weight — days of sparse, purely transactional chat usually produce none.

Imprints is also a membership benefit: without an active membership the whole page is locked behind a Become a member prompt, and new content is not shown.

No. Check-ins only start when Cola is idle; reflections are written at night in the background and the daily recommendations are put together there too, never interrupting what you're doing.

dist/ only contains the runtime entry. Cola needs the root package.json to read the plugin ID, label, entry file, and channel metadata.

Check that the file cola.plugin.entry points to (for example dist/index.js) exists; if it doesn't, run the plugin's own build first, then quit and reopen the Cola desktop app. If it still doesn't appear, check the logs for load errors as described in Troubleshooting.

Bundle runtime dependencies into dist/, or keep a working node_modules/ directory inside the plugin directory.

WeChat is a built-in channel. Built-in channels are managed by the Cola app and are not removed as user-installed local plugins.

A direct message needs its sender.id bound through runtime.identity.bind(), or added to the plugin's allowlist by the owner. A group has to be authorized as a whole, and the message must @mention the bot (deliver it with mentionedBot: true). When neither holds, the plugin replies in the conversation with a hint that authorization is needed.

Check that deliveryContext.to carries enough for outbound.sendText() to find the recipient on the external platform.

Check that config.schema.fields is an array and that each field has key, label, and type.

A locally installed plugin points at your source directory, so there's no need to reinstall after rebuilding. Quit and reopen the Cola desktop app to load the new code.