an obsidian helper that works with your note files

what a bot can do with Obsidian

obsidian work here means working with markdown files on your computer. there's no obsidian sign-in; the bot works with the files. give a local bot the vault as its project folder, then name the folders and notes it may use. separately, the bot keeps its own memory in markdown files, and Open in Obsidian opens those notes.

connect Obsidian

keep the bot on the computer that holds the vault and give it the project folder deliberately. start with a request to list the notes it intends to read. ask for findings in chat before asking for file edits.

for the bot's own memory, open its Memory settings. those notes live under .duskbot/workspaces/<bot>/; they are separate from a project vault you give it.

routines to copy

these routines use files as their source and return proposals in chat. each gives the bot a narrow reading area, so a loose request to tidy your notes does not become a vault-wide rewrite.

every saturday at 10, read the markdown notes in the reading folder of this project. group the questions i left unanswered by topic and include the file name for each. do not edit notes or search outside that folder.

every sunday at 7 in the evening, read this week's notes in the journal folder. summarise commitments i wrote down and separate them from ideas i was only considering. keep the summary in our chat and leave the journal files unchanged.

on the first day of each month at 4, inspect the loose markdown notes at the root of this vault. suggest a destination folder for each using my existing folder names. explain uncertain choices. ask me before you change anything; do not move or rename files yet.

what it asks you first

this is local file work, so connected-app read-only settings are not an obsidian permission boundary. use the bot's computer approval settings and begin on Ask for approval. Auto-accept edits permits file changes, so do not choose it expecting every note edit to pause.

put "ask me before you change anything" in a routine that may propose moving or rewriting notes. the separate sending setting covers emails, messages, posts and payments; it is not the control for a markdown edit.

what it cannot do

• offer an obsidian sign-in or obsidian-specific actions; it works with the note files.
• run a local vault routine while that computer is asleep or dusk bot is closed. a phone paired with that machine also needs it awake to reach the bot.
• treat a cloud-shared folder as a writable local vault. the documented cloud folder sharing is a read-only copy, updated while your computer is on. for editing, use a project folder on your own computer.

your vault is not the bot's memory

a project folder is the material you gave the bot to work with. its own memory is a separate set of notes you can inspect and edit under Memory. turning off Let this bot use memory stops memory use and leaves those files on disk. opening them in obsidian does not make your whole vault the bot's memory.

begin with questions rather than rearranging

for study notes, ask which questions recur across the files you name. for file organisation, ask for a move plan first. if your notes live in a connected workspace instead, the notion integration uses app permissions and a different set of actions.