Obsidian integration
What the planned Obsidian connector is for, how the current connection model works, and what nicoolAI should eventually do with it.
Obsidian is a planned connector for note and knowledge workflows.
The intended role is not generic file access. It is structured note work tied to a user-owned Obsidian environment.
Getting started
To get started with the planned Obsidian connector, open the Obsidian connector setup and connect the vault credentials nicoolAI should use. The setup surface exists, but the broader end-user workflows are still planned.
What it is for
The current implementation shape is built around headless Obsidian sync operations.
In plain terms, the connector is meant to let nicoolAI:
- trigger sync-oriented note workflows
- check note-sync status
- keep the note connection user-scoped instead of shared globally
Connection model
The current connect flow is token-based.
It stores:
- an Obsidian auth token
- an optional default vault path
- an optional config directory
That is a narrower and more explicit model than treating a local notes environment as ambient filesystem access.
What is not live yet
This connector should still be treated as planned from a product perspective.
That means the docs can describe the intended shape, but should not present broad Obsidian workflows as a generally available end-user feature yet.