Skip to main content

FAQ & Troubleshooting

Start with the shortest diagnostic loop:

anyy --version
anyy config
anyy status
anyy doctor
anyy gateway status

These commands identify the selected Profile, resolved Home, configuration health, resident runtime, and common remediation without printing secret values.

General questions​

Is Anyy a local model?​

No. Anyy is the resident assistant runtime. It can use configured remote or compatible/local model endpoints, but the model is a provider route rather than the product itself.

Is Anyy local-only?​

Anyy keeps canonical Profile data locally, but configured model providers, web services, MCP servers and messaging platforms receive data required for the tasks you run. See Data & Privacy.

What is the difference between a Profile, Role, and session?​

  • A Profile isolates data, credentials, configuration, and runtime.
  • A Role changes durable assistant identity inside one Profile.
  • A session is one conversation and its history.

Use separate Profiles when accounts or trust domains must not mix.

Does Anyy remember everything?​

No. Conversation history is stored by session, while durable user facts and preferences belong in Profile memory. Anyy may search previous sessions when the feature is available, but temporary task details should not be promoted to memory automatically.

Can I delete a single session?​

The session.delete RPC can delete an idle Session, but v0.1.107 does not expose a general delete command or button in CLI, TUI or Dashboard. Deleting a Profile removes all of its data and is not a substitute for deleting one conversation. See Session operations.

How much does Anyy cost to use?​

Anyy itself does not make provider requests free. Cost depends on the configured model, reasoning level, context size, media routes, web services, and external integrations. Check the provider's pricing and use /usage or Dashboard usage information where supported.

Installation and update problems​

anyy is not found​

Open a new shell, then inspect the installed Home and PATH. A standard native install places the binary under the Anyy Home's bin/ directory and installs a user-facing entrypoint when permissions allow.

Rerun the installer only after reading its error; it verifies checksums and preserves bounded release history.

Installation reports insufficient space​

Free space in both the temporary directory and Anyy Home. Use ANYY_INSTALL_COMPACT=1 only if you accept less rollback history.

Update completes but Dashboard shows an older version​

Compare anyy --version, anyy gateway status, and Dashboard → About. A manually started old process may still be running. Follow the update remediation rather than deleting releases by hand.

Model and provider problems​

Setup cannot verify the model​

Check the endpoint, protocol, model ID, credential, network access, and provider account limits. Use the installed setup catalog; a model name valid on one endpoint is not automatically valid on another.

Dashboard Chat cannot send​

Open Dashboard → Models and verify a main route exists. Test connection checks catalog access and model membership; it does not test generation. Save the settings, open a new conversation and request a short reply. If fallbacks are configured, confirm which target actually produced it before treating this as verification of the selected model. Run anyy status as well: the Gateway must be reachable.

A media feature does not work even though chat works​

Image understanding, video understanding, image generation, transcription, and TTS are independent routes. Configure and test the specific route; a text model does not imply speech or image endpoints. Dashboard's uploader classifies PNG/JPEG as images and other uploads as files, so uploading an audio or video file there does not automatically invoke media understanding. See Media Understanding.

Reasoning changes increased cost​

Changing effort can invalidate prompt cache reuse. Start a new session after a major effort/model change when predictable context and cache behavior matter.

Dashboard and Profile problems​

Dashboard URL does not open​

Run:

anyy dashboard --status
anyy status

Start Dashboard again with --no-open to print the current URL. Use the This machine URL on the Anyy host; a LAN URL requires a reachable listener and trusted network path.

Dashboard and CLI show different sessions​

Compare Dashboard → About with anyy config. Check --profile, --profile-root, --home, ANYY_HOME, ANYY_DEFAULT_HOME, and the active Profile selection.

A Profile cannot be deleted​

The target must be non-default, non-current, not the active sticky selection, and stopped. CLI deletion also requires --force and refuses nonempty Secrets unless --purge-secrets is explicit.

Sessions look missing after a switch​

Profile switching does not migrate data. Switch back to the original Profile and verify its Home on About/config.

Tool, Skill, and MCP problems​

A tool is configured but not visible​

Check Dashboard → Tools, the session's toolsets, optional backend health, and whether a new session is needed. Credentials, backend health and session scope still determine availability.

For Codemode and deferred tools, also check Codemode and Tool Search. A saved Profile default does not automatically change an existing Session's selection.

A file or command fails​

Inspect the tool result, path or command, operating-system permissions and runtime limits. Enabled tools execute directly. If Chat shows a clarification, answer the missing question or interrupt the run.

A Skill does not appear​

Confirm it is enabled for the current Profile and surface, then run:

anyy skills reload

Retry with the next prompt after reload and check any catalog warnings. System Skills cannot be removed or toggled like user-installed Skills. The managed installer accepts local ZIP packages only; see Skills.

MCP is connected but its tools are absent​

Check the server's enabled state, current offering, exposure and the Session's tool selection. direct tools use model declarations; codemode and deferred tools use the corresponding discovery route when enabled, while hidden tools are unavailable. Probe can help inspect the catalog. See MCP exposure settings.

An @ context reference is blocked​

Protected credential paths, binary files, private/internal URLs, path escapes, oversize content, and sensitive Git changes are refused. Use a smaller safe line range or an allowed public source.

Web problems​

Web search fails​

Open Dashboard → Tools or run anyy tools websearch, verify the provider and credential, and perform its test. Public URL fetching also blocks private network targets.

Messaging problems​

Channel receives no messages​

Run the platform's doctor flow, verify the account is enabled and connected, then inspect DM/group access policy and pairing grants. Some platforms also require webhook reachability or platform-side event subscriptions.

Outbound delivery fails​

Confirm the destination binding, account health, adapter capability, and delivery receipt. A successful tool call without a confirmed receipt may still need platform-specific investigation.

An unknown user can reach Anyy​

Disable the account or tighten DM/group policy, revoke unwanted pairing grants, rotate exposed platform credentials, and inspect recent activity.

Automations and background work​

A Cron job never runs​

Check that it is enabled, the schedule parses in the Profile timezone, the Gateway is resident, and the selected Role/toolsets still exist. In the conversation that created the job, ask Anyy to run that job now, then inspect its completed history and delivery. See Automations.

A scheduled run is waiting​

Open its background conversation and inspect the execution, tool result or clarification. Check model credentials, the delivery route and runtime health.

Background work disappeared​

Check Dashboard's Background sessions and the originating Profile. Use the background/delegation controls in that session; switching Profile changes the visible job scope.

Backup and recovery​

Restore says the target exists​

Restore intentionally requires a new, nonexistent target directory. Choose another path; do not overlay a live Profile.

Restored providers cannot authenticate​

Routine backups omit managed secrets/ and supported mcp/oauth/ directories. Reconnect missing credentials, or restore a protected archive that included those directories. A normal backup can still contain secrets written inline in configuration or Workspace files; all archives need private handling. See Backup & Restore.

Doctor still reports a problem​

Follow the remediation attached to the failing probe, then run the feature-specific status/doctor command. Preserve logs and a debug bundle only after checking it for sensitive content.

Still stuck?​

Collect the minimum reproducible evidence:

  • Anyy version and commit from Dashboard → About;
  • selected Profile ID, with private Home segments redacted;
  • the exact command and safe error text;
  • relevant status/doctor probe names; and
  • what changed immediately before the failure.

Never publish Dashboard token URLs, API keys, OAuth codes, Channel secrets, full environment dumps, private message content, or unreviewed backups.