DocumentationStart here
Build with Impo
An open-source framework for agents, from the conversation to the physical world.
On this page
Three ways into the frameworkWhat comes with ImpoSource and dependenciesRead the status of a featureImpo brings an agent to iOS, Apple Watch, Android, the web, Mac and hardware you build. Your apps, connected services and hardware work with the agent on the Impo server. Talk to it, share context and let it act through the services and devices you connect.
Use the existing apps to experience the system. Fork the framework to change its behavior or add capabilities within the license terms. Connect a board when your agent needs a screen, a speaker or a sensor in the physical world.
Three ways into the framework#
| Start here | What you will learn |
|---|---|
| Architecture | What you can connect and how apps, services and hardware interact with your agent. |
| Extend the framework | Where to add a tool, change instructions, schedule work or build a client surface. |
| Hardware | How to connect a device, describe its capabilities and behavior, and exchange commands and events. |
For a running development environment, go straight to the quickstart.
What comes with Impo#
A conversation that continues. Main Chat keeps a shared history across clients. Other conversations, including each gadget's continuing Conversation, use the Task API. A client subscribes to a run; it does not keep that run alive.
Personal context. Rewind captures audio on the phone. Recordings retains the original recordings and transcripts; Notes shows finished documents based on those conversations. Speaker confirmation selects the user's speech for Memory and Feed. Notes can use the full speaker conversation. See personal context for these different uses.
Permissioned actions. Server tools connect external apps through Composio. Native tools run on the attached phone or Desktop installation with its permissions. Gadget commands use the account-owned gateway route.
Multiple interfaces. Native SwiftUI and Kotlin/Compose apps, a React Web app and an Electron Mac app share an application protocol. Generated cards use a common A2UI catalog. Native permissions and hardware setup differ by platform.
Source and dependencies#
The Impo repository provides its original app, API, worker and shared-contract code under the MIT License. You may use, modify, distribute and host it, including as a service, provided you keep the copyright and license notice. The Impo name and logo are not licensed for reuse.
Third-party materials keep their own licenses. The current Desktop client includes nanoMuse-derived GPL code; its combined distribution remains GPL-3.0-only. See third-party notices. The separately maintained Gadget SDK contains ESP32 firmware and the Linux runtime with original Impo contributions under MIT. Meta-derived portions retain Apache-2.0, and other third-party components keep their original licenses.
The production configuration uses Rebyte for managed agent execution, PostgreSQL for application state and optional services for identity, scheduling, connectors, speech and storage. Available application source does not mean every hosted dependency runs locally. The deterministic development runtime lets you work on the core API without model credentials.
Read the status of a feature#
These guides describe the current source. A Design proposal label marks behavior that has not shipped. In particular, persistent user-created gadget agents, continuous camera observation and the Impo gateway's home-network tunnel remain proposed.
Code and executable contracts are the implementation reference. Each guide links to the relevant source so you can follow a capability from the product surface to its enforcement.