Patricia Filipovic · March to October 2026

What I've built and kept running with Claude

Since March 2026 I've been building personal systems with Claude that run my job search, my mornings and my email. I've become quite comfortable working with AI and maintaining the agents and automations I build, mostly with Claude (Chat, Code, and Cowork) and ChatGPT (Chat and Codex), including connecting them through APIs to other software like Notion.

Claude Code wrote the code at my direction. My part has been deciding what each system should do and catching it when it went wrong. The part I enjoy most is keeping it all in order, knowing what each tool is for and whether it's still worth what it costs.

This page is the record of that work, including the routines that were improved, replaced or retired along the way.

14scheduled jobs tracked in one registry with a weekly health check
3,387notes in Open Brain, my personal knowledge base
460K → 7Ktokens per morning brief after the rebuild
~$151 → ~$50monthly cost of AI job scoring, same model
AI tool operations

The upkeep side of AI, which is the work I like best

These are personal systems with one user, so the scale is small. The upkeep they need is the same kind a team's AI tools need, and I've been doing it every week since July.

Inventory

One registry lists every automation with its purpose, schedule, model, logs and whether it should be running. A weekly check compares the list with what's actually scheduled, and anything running that isn't listed gets flagged. That check found a job that had failed for 9 straight weeks. Each job names its own model, so nothing quietly runs on a stale default.

Use cases and needs

Every new automation starts with the need it serves and a comparison of a plain script against each model size on cost and value. When I reviewed 12 niche job boards, two met the need and were adopted, and the other ten are on record with the reason each was skipped. Retired tools keep a note on why they went, so nobody rebuilds them by accident.

Adoption and usage

Every AI job logs its tokens on each run, and the weekly check reports usage by job. Usage numbers showed a nightly sync spending 690,000 tokens to save about one note. An adoption audit showed my writing corrections almost never reached the knowledge base, so I moved the capture to the moment I make them.

Access

Each job gets the least access it needs. The brief and the alerts read Gmail through a read-only token, and only the cleanup job holds write access, on its own token. Keys live in the macOS Keychain. I trimmed two permission lists that had grown to 242 and 24 one-off approvals, so each unattended task now has one exact permission.

Clean data

Status names live in one file every script reads. Stable IDs stopped duplicate listings, 25 missing application dates were backfilled and marked as estimates, and my labels are saved before any row is archived. Outdated notes get marked superseded so search stops surfacing them, and the nightly backup refuses to overwrite itself with a smaller copy.

How I work

Habits that came out of the work

Each of these started as a specific problem. They're now the rules every new automation has to follow.

Scripts first

Plain scripts handle fetching, sorting and date math. AI only gets the parts that need judgment, and the smallest model that does the job well.

Measure every run

Every job that uses AI records its tokens on each run. Before I build anything new, I compare a plain script with each model size on cost and value.

Nothing disappears quietly

Filtered jobs go to a log, my labels are saved before anything is archived, and the health check reads every error log.

The record says what I said

My career record holds only facts I've confirmed in my own words. Anything Claude inferred waits for me.

Settled stays settled

Once I decide something, it's recorded as final. New evidence gets raised once as a question, and nothing changes until I answer.

Private stays local

My records are versioned in local git with no remote. Alert texts carry a category and a count, never who sent the email.

The logbook

How each system started and changed

Read it by area to follow one system from its first version to now, or as a timeline to see how the pieces grew together. The Fixed filter shows the problems I worked through.

Inventory

Every AI tool and automation I run

This is my registry as of October 2026, in plain language. Usage figures come from the per-run token logs.

ToolUse caseAI usedAccess it holdsUsageState
Job scraper and scoringDaily 6:00amFind new roles and score them against my profileOpus 5, batchPublic job boards, Notion Job Listings, API key in Keychain~$1.41–2.25/runActive
Daily job cleanupDaily 8:45amLearn from my rejections, save labels, archive dead rowsNoneNotion Job Listings0 tokensActive
Target employer sweepSundays 7:00pmCheck employers on my list for new rolesOpus 5, batchPublic career feeds, Notion≤25 jobs, ~2¢ eachActive
Morning briefDaily 7:00amOne page with my day, email that needs me and application statusHaiku 4.5, one callGmail read-only, Calendar, Notion homepage and to-dos, Open Brain~7K tokens/runActive
Email alertsEvery 15 min, 7am–9pmText me when an employer or a bill needs meNoneGmail read-only (shared, never rewritten), Messages0 tokensAwaiting first supervised run
Gmail cleanupMondays 3:00amClear promotions and old mailNoneGmail with write access, on its own token0 tokensActive
Weekly reviewSundays 11:30amFold my corrections into the verified career recordSonnetOpen Brain, Notion review page, local records~350–450K tokens/runActive
Review apply stepDaily 8:00pmApply the changes I approvedNoneNotion review page, local records0 tokensActive
Weekly code reviewSundays 10:30amFind bugs in one changed automation a weekSonnet 5.5, high effortLocal code, read only~25K tokens/unitActive
Health checkSundays 10:00amCompare the registry with what's running, read error logs, report usageClaude task, one scriptOne exact permission, Notion health loglogged weeklyActive
Nightly backupDaily 11:15pmExport Open Brain and commit every record storeNoneOpen Brain read, local git with no remote0 tokensActive
Bills reset1st of the monthUntick last month's Paid boxesNoneOne Notion page0 tokensActive
Notion to Open Brain syncDaily 11:10pmSave notes from my homepageSonnet, only on changeNotion homepage, Open Brain, Calendar0 most nightsPaused
Interactive toolsOn demandWriting, building and reviewingClaude Chat, Code and Cowork; ChatGPT Chat and Codex; Claude and ChatGPT review each other's drafts by copy and pasteConnectors to Open Brain, Notion, Gmail and Calendarbest current modelIn use

Starting an inventory of your own

  1. List every tool and scheduled job in one place, with its purpose and whether it should be running.
  2. Write down what each one can access, and cut it to the least it needs.
  3. Log usage on every run, so cost and adoption show up as numbers.
  4. Compare the list with what's actually running each week. Anything unlisted is a finding.
  5. When something is retired, record why, so it doesn't get rebuilt by accident.
Replaced and retired

What I turned off, and why

Most of my first routines were Claude tasks that did everything inside the model. Rebuilding them as scripts with one small AI call is where most of the savings came from.

OriginalRanWhy it wentReplaced byCost before → after
Four daily email digestsMar–MayHit my usage limit; every slot was scheduled twice; Notion writes timed outRules inside the morning brief, plus text alerts3–5M/day → 0 extra
Morning Window recapMar–JunLost when projects moved folders; mostly empty sectionsMorning brief (script + one Haiku call)460K → 7K/run
Daily GRC job digestApr–MayWeb search was expensive and inconsistentJob board scraper, later two niche boards1.7M/run → scraper
Monthly bills reset taskJunUnticking checkboxes needs no AIPlain script with a once-a-month guard~1M/run → 0
Nightly Notion sync taskApr–MaySpent heavily to save about one note a nightScript with a free change check (paused)690K/run → 0 most nights
Side-by-side scoring testSep 5–10Proved batch and live scoring agree on 236 of 237 jobsSwitched off once proven~$25/month → 0
Two separate job archiversJul–OctOne archived a row before my label was savedOne daily cleanup passno AI either way
Duplicate Gmail cleanup job9 MondaysPointed at a folder, so it never ran onceRemoved; drift check rewrittenn/a
How it fits together

Where things come from and where I see them

Sources

Job boards and employer career sites10 boards, plus fair and target employer lists
Gmail and Google Calendarread-only access for the brief
My chats with Claudecorrections captured as notes as I go

Systems

Job pipelinefilter, AI score, post, clean up daily
Morning briefone script, one small AI call
Open Brain and weekly reviewknowledge base and verified career record
Registry, health check and code reviewwatching all of the above

Where I see it

Notion Job Listingsscored roles, my statuses and reasons
Notion homepageToday and Yesterday, refreshed at 7am
Weekly Review pagechanges for me to approve or reject
A text messageonly when an employer or bill needs me