Overview
Start here for the product view first: what nicoolAI does, where it lives, what is live now, and what is coming next.
nicoolAI is the personal agent for Nicolai.
The product is meant to feel grounded, persistent, and useful in the channels people already use. The point is not to simulate autonomy. The point is to keep the thread, carry the right context forward, and do bounded work when that work should become real.
Two sections, two readers
This docs set is split in two:
- Product guide for the non-technical power user
- Technical appendix for implementation details such as mounts, sandboxes, auth attachment, and runtime rules
If you want to understand the product, stay in the product guide. If you need the implementation model, jump to the appendix.
What nicoolAI does
Today, nicoolAI is strongest at:
- ongoing conversation with continuity
- practical follow-through in message-based workflows
- reading shared Google Drive material when the right account is connected
- staying conservative when permissions or context are unclear
The intended feeling is simple: WhatsApp-native memory, grounded tone, and execution that feels like Nicolai.
What is live now
| Area | Current state |
|---|---|
| Channels | WhatsApp, Slack, web chat, [email protected] |
| Connector | Google Drive |
| Account/setup surface | connector pages and account-linked web setup |
| Safety model | explicit connections, scoped access, fail-closed behavior |
What is planned next
The connector roadmap described in these docs is intentionally narrow:
- GitHub
- Obsidian
- Personal email
Those planned integrations matter because they extend the same product model into repositories, notes, and outbound follow-through without turning nicoolAI into a generic automation layer.
Start here
- How nicoolAI works for the product model in plain language
- Channels for where to talk to nicoolAI today
- Connectors for what nicoolAI can use on your behalf
- Google Drive for the one live connector today
- GitHub integration for the planned repository workflow
- Email Channel for how
[email protected]behaves - Security for access, memory, linked systems, and refusal behavior
- Troubleshooting for the most common failure modes
Technical appendix
Use the appendix when you need the runtime model rather than the product story.