Skip to main content

Product Names and Technical Identifiers

Aico Link is the hardware platform. Aico is the AI Agent that runs on it. The official website is aico.link.

Use Aico Link for boards, firmware, hardware services, USB/Bluetooth device names, and deployment. Use Aico for the Agent's conversation, tools, memory, skills, and voice behavior. The phone application is the Aico companion app.

Canonical Technical Names​

The product naming applies to source identifiers, build artifacts, installed services, configuration, and telemetry:

AreaNames
C++ headers and loggingaico_sdk.h, aico_log.h, AICO_LOG_*
C++ namespacesaico, aico_image, aico_vad, aico_demo
Shared service statusAicoServiceStatus
CMake targets and archivesaico, aico_image; libaico.a, libaico_image.a
Go moduleaico-agent
Python packages and SkillOpt backendaico-benchmark, aico-skillopt, AicoDeviceBackend
Device services and packageaico-agent.service, aico.target, aico-business
Device user/group and runtime pathsaico, /usr/lib/aico, /usr/share/aico, /run/aico
Environment and build variablesAICO_*
Built-in tool skillconfig/skills/aico
OTA signing-key path and boot parameter/usr/share/keyrings/aico-ota.pem, aico.slot_suffix
Backup archive magic and SD filesystem labelAICOBKP1, AICO
APT release metadataOrigin: Aico, Label: Aico business packages
Telemetry trace and tagaico-episode, aico-hardware

Documentation commands and examples use these names. Repository source files, service units, helper scripts, and benchmark suite paths use the corresponding aico spelling. A local checkout may use any directory name; clone examples choose aico-link-firmware explicitly.

Initial Setup and Integrations​

This is the initial Aico release. Build firmware, configure devices, and create integrations using the canonical names above. Use the complete Aico Link firmware image for initial setup, then follow the regular OTA or business package update workflow for subsequent releases.

C++ consumers use the Aico headers, namespaces, and archives. Go imports, service references, environment variables, API clients, benchmark settings, and telemetry queries use the aico identifiers documented here.

The device account is aico with UID 1000. Its home is /home/aico, backed by /userdata/home/aico. The root user's persistent home remains /userdata/userhome. The Agent stores its user configuration in /userdata/agent, its bundled self-knowledge skill uses aico, and managed SD-card data lives under the card's aico directory. Backup exports use the aico-backup format and AICOBKP1 magic.

For deployment and updates, see Deployment, OTA, and Debian Business Packages.

Existing External Names​

Existing GitHub organization, repository, release, and submodule URLs remain unchanged. For example, clone from AidenAI-IO/aiden-firmware, and use the existing signed APT repository at https://aidenai-io.github.io/aiden-firmware/apt.

Sibling checkout paths such as aiden-mcu, aiden-design, and aiden-app refer to those existing repositories; this firmware change does not rename their checkouts or source interfaces.

The companion app is maintained separately. Its currently installed system labels and build identifiers, such as Aiden Ready and AidenLiveActivityExtension, remain accurate references to that app.