3 posts tagged with "Claude Code"

I use Obsidian, so posts about Obsidian × Claude Code / Codex catch my eye when they come across my timeline. And since the start of this year they have gone viral again and again, every few months. No single new app is at the center of it, yet the same theme keeps taking off.

I wanted to try it in my own Vault, but each post says something slightly different. Some are only about folder structure, some tell you to install the official skills, and some bring in MCP. Reading them piecemeal, I could not tell what to start with, or even whether these were competing approaches at all.

So before starting, I read straight through the posts that took off between January and September 2026 and put them back in chronological order. The conclusion: they are not competing. The core idea has not changed once since January. What changes is only which layer is put in front — the compilation rules, the official skills, Codex, MCP, the CLI. What follows is that map.

When I introduced Claude Code into a personal OSS repository I develop and maintain on my own, a requirement emerged: I wanted to keep the AI-related settings and documentation out of the public repository and operate them locally only. In this post, I focus on the two topics I spent the most time considering — the use cases for exclusion settings, and the design of history management, which tends to become scattered in AI-assisted workflows.

Today I'm releasing Ollama Colab Free Server, an open-source notebook that runs Ollama on Google Colab's free GPU and makes it instantly available as a backend for Claude Code and Continue. Execute the cells top to bottom, and a publicly accessible LLM server is up within minutes.

The setup steps and usage of this tool are explained in detail in the technical documentation.