How I Take Daily Notes in Obsidian with Claude Code (Automated AI Workflow)

CCoding With ADHD
컴퓨터/소프트웨어창업/스타트업AI/미래기술

Transcript

00:00:00Now that we have everything set up, let me show you my actual workflow.
00:00:03If you haven't seen part 1 where we set up the vault and folder structure,
00:00:08make sure to check that out first. I'll link it in the description.
00:00:11To get started, just type clod and then run the /init command.
00:00:16This tells clod to add a clod.md file to your vault.
00:00:20As you can see, it now has context about our vault. The folder structure, conventions,
00:00:27everything clod needs to understand how this system works. I'll cancel out of this since I've already
00:00:32done it. This is how I take notes using Obsidian Clipper and Clod Code to summarize them into my
00:00:38daily journal. And by the way, the same approach works with any AI agent CLI you prefer. I just
00:00:45happen to use Clod Code. So the first thing we need is Obsidian Clipper. This is an official plugin by
00:00:52Obsidian and it's honestly a game changer for capturing information while you're browsing.
00:00:58You can download it by heading over to their website. I'll drop the link in the description.
00:01:03It's a super useful extension that lets you clip and save content directly to your vault
00:01:09without leaving the page you're on. No more copying and pasting, no more switching between tabs and
00:01:14losing your flow. Just grab it for your browser of choice. I'm using Safari, so I'll click here
00:01:19to download the Safari version. Once it's installed, you'll see the Clipper icon in your browser toolbar.
00:01:25And that's it. You're ready to start capturing. Let me show you how I actually use this thing.
00:01:30I've set mine up to automatically move clipped notes to my inbox directory. You can change this
00:01:37in the extension settings if you prefer a different location. But here's the thing. Whenever I clip a
00:01:44website, I also want it captured in my daily journal. By the way, I've updated the generator
00:01:52daily template a bit since part one. It now has front matter, which makes things more structured.
00:01:58I can track additional information about my notes like tags and the current date. I've also added
00:02:06this templater function called cursor, which automatically moves your cursor to that line
00:02:13when the note opens. Super handy. The template also has navigation links to quickly switch
00:02:20between yesterday and tomorrow. So now, whenever we click on daily note, it uses this new template.
00:02:29As you can see, everything's in place. Cool. Back to the main topic. What I really want
00:02:38is a quick summary of everything I've captured during the day. So whenever I clip something,
00:02:44I want to automatically generate a summary, create a markdown link to the clip note,
00:02:50and add a short description, all inserted directly into my daily journal.
00:02:56So how do we actually make this happen? We need a script that handles the summarization
00:03:05and links everything together. Okay, let me go ahead and create a new directory called
00:03:11scripts inside the system folder. This is where I like to keep all my automation scripts,
00:03:18just keeps things organized and easy to find. I've already created the script by asking cloud code to
00:03:24do it for me. Now, one thing I should mention, Obsidian doesn't show file formats other than
00:03:29markdown by default. That's why these files appear empty here. To fix that, just go to settings,
00:03:35then files and links and toggle on show all file types. Now if you go back, you'll see the files
00:03:41are actually there. I also asked cloud to generate a Windows version of the script, which is in
00:03:47PowerShell. By the way, PowerShell is a cross platform automation tool. So it actually works
00:03:52on all platforms if you prefer it. For the Mac OS version, I decided to stick with bash. So I
00:03:59asked cloud code to use fswatch and launchd to create a launch agent that starts automatically
00:04:05on login. If you're not familiar, fswatch is a file monitoring tool that watches for changes
00:04:12in a directory. And launchd is Mac OS's built in system for running background services. Together,
00:04:19they make sure our inbox watcher runs silently in the background without us lifting a finger.
00:04:26As you can see, cloud generated a plist file. That's the launch agent configuration and saved
00:04:33it to our scripts directory. It even gave us the exact steps to set it up. First, we need to make
00:04:39sure fswatch is installed. Just run brew install fswatch if you haven't already. Next, we installed
00:04:47the launch agent by creating a symbolic link from our plist file to the launch agents directory in
00:04:53our home folder. And finally, we load it using launchctl load. This starts it immediately and
00:05:01makes sure it runs on every login. And that's it. Now every time you log into your Mac, the watcher
00:05:09starts automatically. Clip a website and it shows up in your daily journal, completely hands-free.
00:05:15This is the kind of setup that just works in the background while you focus on what actually
00:05:21matters. If this was useful, hit the like button and subscribe. It genuinely helps the channel a
00:05:27lot. I'm going to keep sharing practical stuff like this, so stay tuned. And if you have any ideas,
00:05:34questions, or things you want me to explore next, drop them in the comments. I actually read them.
00:05:40Thanks for watching and I'll see you in the next one.

Key Takeaway

Integrating Obsidian Clipper with a Claude Code-generated fswatch script automates the summarization and linking of web captures directly into daily journals upon file creation.

Highlights

  • The /init command in Claude Code generates a clod.md file that provides the AI agent with full context of the Obsidian vault structure and conventions.

  • Obsidian Clipper captures web content directly to a specified inbox directory to prevent workflow interruptions during browsing.

  • A custom daily note template uses a Templater function to move the cursor automatically to a specific line and includes navigation links for adjacent dates.

  • The automated workflow uses fswatch to monitor the inbox directory and launchd to run the summarization script as a background service on macOS.

  • A symbolic link from the plist configuration file to the LaunchAgents directory ensures the monitoring service starts automatically upon system login.

Timeline

Initialization and Vault Context

  • Running the /init command creates a clod.md file within the Obsidian vault.
  • The clod.md file stores directory structures and folder conventions to inform the AI agent's operations.

Setting up the environment requires establishing a baseline of knowledge for the AI agent. This file acts as a map for Claude Code, allowing it to understand where to find files and how to follow existing organization rules. This initialization step is necessary before executing more complex automation tasks.

Web Capture with Obsidian Clipper

  • The official Obsidian Clipper browser extension saves web content without manual copying and pasting.
  • Configuring the extension settings directs all clipped notes to a dedicated inbox folder for centralized processing.

The workflow relies on the official browser extension available for major browsers including Safari. By automating the transfer of web data to the vault, the system eliminates the friction of switching between tabs. Directing these clips to an inbox folder creates a predictable trigger for subsequent automation scripts.

Enhanced Daily Note Templates

  • Structured front matter allows for consistent tracking of dates and metadata tags within daily notes.
  • The cursor function in Templater places the focus on a specific line immediately upon opening a new note.

Daily notes serve as the destination for automated summaries and links. The template includes built-in navigation for moving between yesterday and tomorrow's entries. These refinements ensure that when the automated script appends information, the note remains organized and easy to navigate.

Automated Summary Script Generation

  • Enabling the 'show all file types' setting in Obsidian allows non-markdown scripts to be visible in the file explorer.
  • PowerShell provides a cross-platform option for running automation scripts on Windows and other operating systems.

The system uses a dedicated scripts folder within a system directory to house automation logic. Claude Code generated both Bash and PowerShell versions of the script to handle summarization and linking. Users must adjust Obsidian settings to see these files, as the application defaults to showing only markdown content.

Background Execution via Launch Agents

  • The fswatch utility monitors the inbox directory for new file additions in real-time.
  • macOS uses launchd and plist files to manage background services that persist across system restarts.

A launch agent configuration allows the file-watching service to run silently in the background. Setup involves installing fswatch via Homebrew and creating a symbolic link to the user's LaunchAgents directory. Once loaded via launchctl, the system automatically summarizes new clips and appends them to the daily journal without further user intervention.

Community Posts

View all posts