Aicoo is not only a chat box. It is a set of reachable surfaces for users, guests, coding agents, and partner products. Pick the surface based on who needs access, what context they should see, and whether the workflow should live inside Aicoo or inside your product.
Aicoo App
- Primary workspace: Users review notes, todos, conversations, shared links, background work, and connected tools in one command center.
- Direct chat: Users can ask questions, delegate work, inspect project context, and trigger approved tools.
- Owner controls: The app is where users manage what Aicoo knows, which links are active, and which integrations are connected.
Aicoo Skills
- Repo-connected agents: Aicoo Skills let developer agents connect Aicoo to a local workspace or repo, then sync project docs, decisions, handoffs, and working context into Aicoo.
- Agent-side actions: Skills can search notes, read context, create or edit notes, save snapshots, create share links, and keep an agent's knowledge up to date without leaving the developer workflow.
- Best fit: Use Skills when someone is building in Codex, Claude Code, or another agentic IDE and wants Aicoo to remember the project instead of losing context between sessions.
Shared Agent Links
- Guest access: Share a scoped Aicoo agent with collaborators, mentors, candidates, customers, judges, or event participants.
- Controlled context: Link recipients interact only with the folders, notes, tools, or permissions the owner chose to expose.
- Product embedding: A host app can create links for teams, projects, submissions, profiles, customer records, or partner intake flows.
Product APIs
- Backend workflows: Your server can sync notes, create folders, manage todos, create share links, execute approved tools, and read conversations through the OS API.
- Custom UI: Your product can keep its own interface while using Aicoo for memory, agent answers, and operational follow-through.
- Hackathon flows: Event platforms can create team or project agents, then let mentors and judges ask questions through scoped links.
iMessage (To Be Released)
- Quick capture: iMessage is planned as a lightweight way to send short requests, reminders, decisions, and handoff notes to Aicoo.
- Personal follow-through: The expected use case is fast mobile coordination: "remember this," "follow up tomorrow," "summarize this thread," or "add this to my project context."
- Status: This surface is not the default production integration path yet. Use the app, Skills, shared links, or APIs for current developer builds.
Connected Channels
Aicoo can also appear through connected communication or productivity channels when enabled for an account. Examples include email, calendar, team chat, meeting tools, and external SaaS apps. These are integrations, not the core product surface, so they are covered separately in Integrations.
For implementation details, start with Build with Aicoo + API or open the API Reference.