Feature Overview
Anyy is a resident personal assistant. Its features are organized around sessions, memory, tools, background work, channels, provider routing, and local runtime control.
This page is a map. Use it to choose the right entry point instead of reading the reference pages first.
Core Features
| Feature | Use it for |
|---|---|
| Tools & Toolsets | See which model-callable tools can appear in a turn and how toolsets control visibility. |
| Toolsets | Configure default toolsets, per-turn toolset selection, and optional connector toolsets. |
| Persistent Memory | Store durable user facts, preferences, and assistant notes in USER.md and MEMORY.md. |
| Context Files | Understand profile and role identity files such as SOUL.md. |
| Context References | Attach explicit file, folder, URL, git, and tool-result references to a turn. |
| Artifacts | Work with generated or attached artifacts such as images, audio, video, and files. |
| Approvals & ChangePlans | Review state-changing actions before Anyy executes them. |
| Audit | Inspect recorded tool, approval, config, connector, and MCP events. |
Core features share the same trust model: visibility does not imply permission. A tool can be visible and still require approval, a ChangePlan, or audit.
Automation
| Feature | Use it for |
|---|---|
| Cron | Run scheduled agent, skill, notification, reminder, or script jobs. |
| Background Jobs | Track resident work that can outlive the foreground reply. |
| Tasks | Keep durable personal task records. |
| Delegation | Split bounded model work into child sessions. |
| Workflows | Track grouped background work with a parent workflow job and child jobs. |
| Heartbeat | Monitor runtime liveness and failure notifications. |
Use tasks for passive work items, cron for time-based execution, background jobs for async work, and workflows when related child jobs need one parent handle.
Media And Web
| Feature | Use it for |
|---|---|
| Web Tools | Search, fetch, and extract public web pages. |
| Browser | Connect a managed browser MCP server as the browser capability. |
| Image Generation | Generate images as scoped artifacts. |
| Text To Speech | Generate audio attachments from text. |
| Transcription | Convert inbound audio attachments into turn text. |
Media features are optional. They appear only when the matching provider, model, driver, connector, or turn metadata is available.
Management
| Page | Use it for |
|---|---|
| Configuration | Understand config.yaml and setup-managed fields. |
| Configuring Models | Set the main model, auxiliary model slots, and fallback routing. |
| Roles | Manage profile-local role identities and SOUL.md files. |
| Dashboard | Use the resident dashboard sidecar. |
| Gateway | Run the resident gateway and understand runtime boundaries. |
| Status And Doctor | Inspect runtime health, logs, usage, audit, and doctor checks. |
For compact field tables, use the Configuration Reference, Provider Config Reference, and MCP Config Reference.
Skills
| Feature | Use it for |
|---|---|
| Skills System | Understand how Anyy discovers and presents skills. |
| Skill Management | Install, toggle, remove, reload, and inspect skills. |
| Skill Authoring | Write reusable skill instructions for Anyy. |
Skills are instructions and supporting files. They are not MCP servers, and they do not grant extra tool permissions by themselves.
Integrations
Integration pages keep setup details in one place:
| Integration | Entry point |
|---|---|
| Providers | Provider Integrations |
| MCP | MCP Integration |
| Browser | Browser Integration |
| Media | Media Integration |