Laura Rosenberger

Tag: Claude Code

  • How I optimise my Claude usage limits by running tasks overnight

    Claude's usage limits come in five-hour windows. I kept bumping into them during the day, then sleeping straight through several windows every night. Capacity I'd paid for, completely unused.

    At the same time, I end most days with tasks that Claude could do without me. Build this tool. Research that topic. Tidy up those notes. None of them need me at the keyboard. They just need a decent brief.

    The Solution

    I tag a task 'overnight' in my to-do list app, and my Mac does it while I sleep.

    In the evening, a small script picks up anything I've tagged, turns the note into a job, and works out which project folder it belongs to. At 2am the Mac wakes itself up and Claude Code works through the queue – a fresh session for each task, in the right folder. By the time I sit down in the morning, the results are waiting for me.

    How I Use It

    The to-do note is the brief, so I write it as if I'm handing the task to a person: what I want, where the relevant files live, what good looks like. A lazy note gets a lazy result.

    A recent example: I came across this list of signs of AI writing (https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing) and wanted to create a 'slop checker' skill to run over my writing before I publish anything. I wrote that up in a to-do, tagged it 'overnight', and went to bed. By morning Claude had built the skill and tested it against sample documents.

    Why This Has Impact

    The most obvious change: I run out of my Claude allowance far less during the day, because a chunk of my work now happens in windows I used to sleep through.

    The change I didn't expect: it's making me more specific. There's nobody at the keyboard at 2am to nudge things along, so the brief has to be clear enough that Claude gets it right without me intervening or guiding. That discipline is making me better at writing specific prompts, and at giving Claude access to the context that lets it run more autonomously than if I was babysitting it.

  • AI Memory Across Sessions

    One of the reasons OpenClaw has captured everyone's imagination is the memory. It remembers you. Every other AI conversation starts from zero – close the window, lose everything, re-explain yourself next time.

    I've been working a lot in Claude Code, and have built myself a little skill to recreate this.

    How It Works

    I built a /handoff command that runs a structured wrap-up when I'm done working. It reviews the session and saves what matters to a set of persistent markdown files — a daily note, active threads, behavioural patterns (which it can then pull me up on…), and self-improvement notes.

    These notes are accessible for future sessions. Claude knows what I was working on, what's due, and what patterns to watch for.

    The whole thing is just a text file telling Claude what to do and what to save – but it is making using Claude Code as a general assistant for non-technical work just so much better.

    Why It's Useful

    It turns each session from a one-off into something that compounds. Less time re-explaining, more time working. And it catches things I wouldn't note myself — like when the same blocker keeps showing up or when I'm quietly avoiding something (ahem).

    It's not as seamless as OpenClaw's built-in memory. But I control what gets saved, where it lives, what gets forgotten and what my 'assistant' is able to do with this information.

  • The Imagination Gap

    AI is asking you to imagine something you've never seen. And it's hard to be what you can't see.

    I was speaking to the CEO who said 'we lack the imagination to even know what's possible', and it really stuck with me.

    Unless you're really into AI, it really is hard to see what to do beyond 'get ChatGPT licenses for everyone' because how are you supposed to know what's possible when very few people in this space are pushing the boundaries?

    The way I'm trying to bridge this 'imagination gap' for consumer brands is by taking inspiration from the businesses and the individuals who are operating right at the edge.

    Here are 3 sources of inspiration for me at the moment:

    'Companies as Code'
    If AI can do extraordinary things when given a set of 'skills' – essentially just well-structured text files – what happens when you codify your business in the same way? Your processes documented, your data accessible, your operating system written down in a form that AI can act on. So you don't just aim to be a consumer brand that uses AI, but a consumer brand whose operations are built to run like software.

    AI driven software development
    I spent time with a group of AI engineers who weren't just using AI to write code. They'd built entire systems where AI writes the code, tests it, catches its own mistakes, and iterates until it works. Their focus wasn't on building software. Instead, they'd built the machine that builds software. What's the equivalent for a non-technical business?

    See also – compound engineering.

    Claude Code for knowledge work
    Claude Code for non-technical use cases has been having a moment (and OpenClaw is Claude Code in a trench coat). If you want to really geek out, explore the Claude Code+Obsidian combo. Claude Code has become the default way in which I work and am building my consultancy business.

  • Claude Code Plugin for Obsidian

    Last year I moved all my notes and files out of Notion and into Obsidian. With Notion, you're locked in to whatever tools they give you. I wanted to be file-first rather than software-first, so I could use the latest AI tools on my actual files.

    I was already using Claude Code to work with my files. Then I found a community plugin for Obsidian that adds Claude Code as a sidebar. I now have access to Claude Code and everything it can do right where my notes are.

    The Solution

    I installed the Claude Code plugin from Obsidian's community plugins. It adds a sidebar where I can have conversations with Claude Code whilst viewing my files. There's a button to link specific files into the conversation, so Claude has context on exactly what I'm working with.

    This isn't just having a conversation with Claude, this is Claude Code, which means it can take actions, plan, and has all the power that Claude Code has rather than just Claude, which has been way more useful.

    How I Use It

    As a practical example, I keep Markdown files for potential clients in my CRM folder. After a sales call, I use the sidebar to automatically pull in transcripts and add my personal notes and thoughts to create really high-quality notes about each client. It updates the metadata properties at the top of the file. That's how I track what needs to happen next – things like 'awaiting proposal' or 'follow up in two weeks'.

    I can also ask it, 'Who do I need to follow up with?' and it'll search my CRM notes and draft emails for each person.

    The whole thing takes a fraction of the time it used to, and to be honest, this kind of thing I often used to not be super on top of because it felt like a chore. Now I actually do it, or rather, now it gets done for me.

    Why This Has Impact

    Better follow-ups, less prep time before meetings, and I can easily search my notes to find who might be a good fit for something.

    The bigger win is flexibility. I'm not locked into any specific tool. My notes are just Markdown files. If a better AI tool comes out tomorrow, I can use it on the same files. File-first means I control my data and what I can do with it, instead of being locked in.