Local-agent discovery and conversation
Desktop and native client code contains local and explicitly configured agent adapters and conversation flows.
Product
A local-first Human-Agent Collaboration Client.
LicoUp gives people one conversation-oriented client for working with visible AI agents while keeping approval, sensitive runtime data, and local effects under endpoint control.
Definition
One human-facing layer across many agent runtimes.
LicoUp connects different agent runtimes through explicit adapters and projects them into one durable conversation model.
The product starts with local and explicitly configured agents, then grows the same conversation model toward human messaging, peer endpoints, federation, recovery, and multi-device continuity.
Conversations, context, and control.
The client brings these pieces into one conversation model. See current compatibility for the agents and setup requirements that apply today.
Canonical Conversation backend
A Rust-owned indexed SQLite/WAL authority stores conversations, memberships, structured events, topology-neutral graph snapshots, and private runtime bindings.
Assistant workflow and Subagent MCP
Assistant-facing profile, execute, inspect, and cancel surfaces support temporary workflows under the canonical conversation authority.
Gateway Runtime
Source includes one gateway process for the local LLM gateway layer and admitted communication channels.
Roadmap
Expand the same model across agents, devices, and networks.
| Area | Direction |
|---|---|
| Peer endpoint protection | Preview endpoint protection provides the current path toward a complete pinned Lico Arc Protocol Line. |
| Lico Arc protocol execution | LicoUp is designed to execute pinned Lico Arc protocol lines as the protocol definition matures. |
| Federation and multi-device history | Extend the durable conversation model across independently controlled endpoints while preserving endpoint authority. |
| Official network | Provide a convenient replaceable network entry point while keeping the client usable with other compatible deployments. |
| Release channels | Progress direct and store distribution lanes independently across desktop and mobile targets. |
Design philosophy
Diverse. Connected. Open. Integrated.
Diverse: adapters connect different agents and devices without making one vendor the product boundary.
Connected: local tools and peer clients share a clear, inspectable flow.
Open: source and client contracts are reviewable and extensible.
Integrated: UI, bridging contracts, Rust domain logic, infrastructure, and native OS adaptation have explicit architectural boundaries.