Building KraigOS: the devlog

Aug 25, 11:19 amdesign

Rules before code

Codex: Wrote the build rules before any code: work in gates, stop at every gate for my approval, and never build for a need that hasn't shown up yet.

• Two stores only: a rulebook of my standing decisions, and one database for everything that changes. No second copy anywhere.
• One command, next, would give me the single most valuable thing that needed my attention.
• A budget for my own time: routine upkeep should take under 30 minutes a week.

What happened next: The one-database rule outlived everything else from that day. It's still the first rule KraigOS follows.

Aug 25, 1:22 pmbuild

The first real loop

Codex: Built a small kernel that answered questions from real records, and proved it on live work the same afternoon.

• A task went in, came back as a recommendation, got done, and its outcome was saved: the whole loop, on real work.
• Every change to a record is attributed and can be undone, and retrying a change never doubles it.
• That night it pulled in the useful parts of my older notes.

Aug 26, 1:19 pmbuild

Memory for conversations, people and posts

• Records of my AI conversations, so decisions made in chat weren't lost.
• A small memory of the people I work with.
• A tool that could publish exactly one approved post to X, and a review-only draft trigger for it.

What happened next: All three were rebuilt more simply later. The idea that a chat is a source of facts, like an email, stayed.

Aug 28, 9:14 pmemail

Chasing inbox zero

• Inbox work aimed at a literal zero, with a judgement layer that decided what each email needed.
• Replies went out only as the exact text I had approved, checked again after sending.
• A second AI agent in the cloud was wired in to work the inbox.

What happened next: It worked, but every safeguard added another layer. An attempt to put the inbox on autopilot was stopped on Sept 6, fixed and switched on the next day.

Sep 3, 2:36 pmbuild

My voice, work contracts and a lab

• A model of how I write, built from my own sent mail: short, plain, no em dashes.
• Work contracts: what done looks like for each piece of work.
• An automation lab, where new automations ran in shadow before they could act.

What happened next: The voice rules survived almost word for word, and the lab's habit of running new automation in shadow first came back with every worker after.

Sep 20, 8:22 amlesson

77,000 lines

Codex: Added an orientation file so a new session could find its way around, which says how big it had become.

• Pipelines for two mailboxes, a cloud runtime, the second agent, tools for a podcast and for X, the automation lab.
• About 77,000 lines of code, guarded by an 850-test suite.
• Every change still needed a gate, a test run and my approval.

What happened next: Three days later all of it was replaced.

Sep 22, 4:17 pmsafety

Backups, without asking me

“i want this backup process automatic”Kraig, Sep 22, 4:13 pm

“i don't want to have to approve entry like this”Kraig, Sep 22, 4:14 pm

• A nightly backup of the database and the code to my Google Drive, checked each time, with no approval step.

What happened next: Retired three days later, when the database moved to Cloudflare and the code started going to GitHub on every change.

Sep 22, 7:01 pmdesign

Keep the meaning, not the raw files

“i really don't want to save retained evidence. once info has been processed into KraigOS, i don't want to keep the large raw files for no reason”Kraig, Sep 22, 6:08 pm

“i'll just always keep the raw videos and photos separate from KraigOS. I always archive them on my own anyway.”Kraig, Sep 22, 6:55 pm

“retire podcast search and chatgpt history”Kraig, Sep 22, 7:28 pm

• KraigOS keeps what a file means, in a form Claude can use, not the file itself. Photos and videos stay in my own archive.
• Two tools nobody used, a podcast search and a search of old ChatGPT history, were retired.

Sep 23, 2:12 pmbuild

Into my own Cloudflare account

“I just want to be able to use KraigOS and do work... using my phone while my mac stays home and open”Kraig, Sep 23, 9:32 am

“go with option 1. we're moving email to gmail as well”Kraig, Sep 23, 1:25 pm

Claude: Moved the database into my own Cloudflare account, with a small program in front of it that Claude reaches as a private connector from any Claude app.

• KraigOS works with my Mac closed, from my phone or any Claude chat.
• The old database on the Mac became a read-only archive in Google Drive. There is still only one live store.
• My email moved into one Gmail inbox that the new email worker could watch.

Sep 23, 3:16 pmemail

An email worker, in shadow

Claude: Gave the new program its first job: read every email as it arrives and decide what it needs, but only log the decision.

• Every email sorted into one of three lanes: low stakes, routine but real, and high stakes, which are left to me.
• When it's unsure, an email goes up a lane, never down.
• A private page where I could see each decision and mark it right or wrong.

What happened next: It stayed in shadow for less than a day.

Sep 24, 10:41 amemaillesson

Save the signal first

“it's super important for KraigOS that email be my main funnel and point of collection for signal and value. And if the system is just archiving emails and letting the signal and data pass through without actually extracting the value or adding it to KraigOS if it needs to, like that's a huge problem.”Kraig, Sep 24, 10:15 am

Claude: Rebuilt the worker around one rule: nothing leaves the inbox until what it says is saved.

• Every email, and every reply I send, is read whole. Dates, offers, people and changes go into KraigOS, each with the email as its source.
• Its writes only ever add: new records, new facts, reopened items. It never deletes or rewrites.
• Low-value mail is archived with a label after its signal is saved, and when I move one back, that counts as a correction.

(open full size)

Sep 24, 1:37 pmdesign

My chats are signal too

“signal and data from claude convos and claude code sessions should be added to KraigOS when it's useful”Kraig, Sep 24, 1:28 pm

“this should all happen automatically while i use claude”Kraig, Sep 24, 1:31 pm

• Whatever I decide, finish or mention in a Claude chat is saved to KraigOS as it comes up, citing the chat.
• Same limits as email: it only adds, and nothing is sent, paid or deleted because of it.

Sep 24, 3:48 pmfilms

A catalog of every film

“KraigOS should have a catalog of like all of the videos that I've made and like whatever relevant information might be helpful alongside.”Kraig, Sep 24, 3:14 pm

• Every long film on my channel is a row in KraigOS, with its type, era, music and rights.
• Changes to the catalog are kept as history.

What happened next: It became the spine for everything after it: the shorts ledger, translations, the search of every shot, and the music library.

Sep 27, 1:25 pmsocial

Comments and DMs, through KraigOS

“a worker who constantly checks all of my social media and replies when it's smart with full context to KraigOS to make judgement and references better”Kraig, Sep 27, 1:05 pm

• Claude can read new comments and messages on my Facebook Page and Instagram, and post a reply only with my OK on the exact text.
• Every reply and every skip is logged, so nothing is answered twice.

What happened next: Instagram DMs stayed off: the platform wouldn't return my message list without a higher level of access.

Sep 27, 9:29 pmbuild

Pings on my phone

“a phone notification would be great. i'd like to get more than i need and scale back when i want rather not get enough notification about what's happening, especially when it's automation”Kraig, Sep 27, 6:59 pm

• My phone got a ping for everything the automation did, with a Cancel or Undo button on anything it was about to send or had posted.

What happened next: The free service it started with refused most of the pings the first night, so the next day they moved to a free Telegram bot. Two weeks later I turned them all off.

Sep 28, 9:28 amsocial

A social media manager for my accounts

“i want the worker to be a professional social media manager for my accounts. it should use KraigOS and full context of my work to answer questions well and actually add value...”Kraig, Sep 28, 9:02 am

“this all looks good but i don't want to have to approve it. let's fully automate this now”Kraig, Sep 28, 9:04 am

Claude: Had built it to draft in shadow the night before. With my go-ahead it started posting on its own.

• Every half hour it read new comments, decided whether a reply beat silence, and answered in my voice with the context of the film, the route's guide and my gear page.
• Brands, money, press and anything sensitive always went to me. Every posted reply could be undone with one tap.
• A daily cap on how many replies it could post.

What happened next: Three days later it was replying too often and pushing the same link. See Oct 1.

Sep 28, 10:13 amemail

Simple email answered on its own

“all three are good”Kraig, Sep 28, 9:54 am

“the more we can automate with this 24/7 worker the better.”Kraig, Sep 28, 9:56 am

Claude: Proposed three kinds of automatic reply for first-contact email.

• First-contact fan questions got a short answer from my public pages, and a couple of kinds of email got a reply pointing to the right page.
• Each reply waited 15 minutes with a Cancel button, and anything touching money, deals or people I already work with was held for me.

What happened next: On Oct 12 I paused every automatic reply. Since then a reply goes out only after my yes on the exact text.

Sep 28, 10:22 amlinks

Affiliate links, read and repaired

Claude: Connected KraigOS to Geniuslink, read-only at first, and built a tool to swap old links in my YouTube descriptions for my own short links.

• Clicks by link and country, and links that are broken or out of stock.
• A daily check for newly broken links.
• Description edits are previewed first and keep every translation on the video.

What happened next: On Oct 1 Claude could make new links, never duplicates. On Oct 9 I gave a standing OK to re-point broken links. On Oct 12 the daily check became a quarterly sweep, since a few broken links a quarter cost less than checking every day.

Sep 28, 10:57 amcalendar

The worker keeps my calendar

“all reminders work best as google cal events”Kraig, Sep 24, 12:14 pm

“yes let's promote the worker to manage my google calendar automatically 24/7”Kraig, Sep 28, 10:41 am

“it's better to give me more events and more reminders and more stuff. And then it's easier for me to scale back once it's annoying”Kraig, Sep 28, 2:47 pm

• Anything with a date gets a private event, and anything I have to do by a date gets a 10am reminder.
• Events move when the dates change and go away when the work closes. It only touches events it made.

What happened next: The calendar was the first part on autopilot under the routine on Oct 12, and it still is.

Sep 28, 2:42 pmlesson

How Claude should work with me

“stop asking me to do things. you check it”Kraig, Sep 28, 12:34 pm

“the long list of questions was just too much for me to do. So like, ask me the questions one at a time”Kraig, Sep 28, 2:42 pm

“you keep not doing things i'm asking you to do and stopping too early and asking me to do things when you could just do them. it's annoying”Kraig, Sep 30, 9:44 am

• One question at a time, each with Claude's recommendation and a default.
• Claude checks things itself instead of asking me to watch or check.
• When a route is blocked, Claude tries the other allowed routes before handing anything back.

Sep 28, 5:30 pmsafety

A security review, and nine fixes

Claude: After a day of shipping, reviewed the whole program for security and reliability and listed nine problems. All nine were fixed that evening.

• Text from emails and comments can never act as instructions, for the workers or for any Claude session.
• Two overlapping runs can't post the same reply twice.
• A mistyped limit falls back to a safe default instead of switching the limit off.

Sep 29, 12:43 pmposting

A posting queue

“Yeah, you can start that.”Kraig, Sep 29, 12:02 pm

Claude: Proposed the first phase of a posting queue.

• Claude queues my finished videos and photos for Instagram and Facebook and picks the times; a small job publishes each one on time.
• A new format starts in review, where every post waits for my OK. Once I approve the format, its posts go up on their own.
• Every post can be taken down with one tap, and anything made with AI carries the platform's AI label.

What happened next: On Oct 11 Facebook went back to posting by hand, because posts made through the API reached far fewer people. The queue now covers Instagram only.

Sep 29, 1:45 pmfilms

My films in six more languages

• Titles and descriptions written in Spanish, German, Portuguese, French, Italian and Japanese from the English ones.
• Links, handles, codes and timestamps are locked so a translation can't change them; one that loses one isn't used.
• Every translation is previewed, and an update never wipes the others on the video.

What happened next: On Oct 7 I gave a standing OK to apply them without asking when every check passes. The back catalog is on autopilot.

Sep 29, 1:45 pmemailsafety

Only decisions reach my inbox

Claude: Went through a batch of what the worker had kept for me and found mail that only informed me, with nothing for me to decide.

• Mail that only informs me, like statements, notices and confirmations of things I already did, is archived once its facts are saved.
• A fact that repeats one already saved attaches to that record instead of making a new one.
• Passwords, codes and keys that show up in email are blanked out before anything is stored.

Sep 29, 3:50 pmfilms

Every shot, searchable

“Yeah, that sounds good.”Kraig, Sep 29, 11:55 am

Claude: Proposed the split: KraigOS holds a written description of every moment in my films, and Google Drive keeps the footage.

• Each moment: what's in the shot, the light, the mood, the sound, how good it is and what it's good for, with its file and its time in the film.
• Search by plain words. Emails and phone numbers are stripped out before anything is stored.

What happened next: Gemini's logs of my films went in from Oct 2. The database's free tier caps writes per day, so the load was spread over several days. Today it holds 48,800 moments from 242 films.

Sep 30, 10:52 amsafety

A daily backup of everything

“The daily database backup, you can deploy that.”Kraig, Sep 30, 11:27 am

• Every morning, every table is copied, compressed and checked into private storage in my own Cloudflare account.
• The first copy of each month is kept forever; daily copies for 35 days. A monthly copy also goes to Google Drive.
• Restoring builds a plain database file on my Mac, never over the live one.

Sep 30, 11:17 amemaillesson

The email worker's first report card

“option 3”Kraig, Sep 30, 10:13 am

Claude: Measured the first week: about 79% of the worker's judged decisions were right. Laid out three options: switch it off, narrow it, or keep it and fix it. I picked the third.

• A weekly review of its decisions, with the accuracy trend in one line.
• A retrain: a search that crashed on long text was fixed, one bad email can no longer hold up the rest, and it states keep or archive for every email.

What happened next: By Oct 11 it was accurate enough but expensive. Its job moved to the KraigOS routine on Oct 12.

Sep 30, 12:50 pmemail

People, from my own email

“I feel like you should have had this information in my like contacts or relationships info in KraigOS.”Kraig, Sep 30, 12:15 pm

“Yeah, you can deploy that and do the catch-up.”Kraig, Sep 30, 12:52 pm

• One record for each person I've actually traded emails with: how I know them and what we've worked on.
• Matched by address first, never duplicated. Unsure matches wait for review.
• A catch-up from the past year of my own mail, reviewed before anything was added.

Oct 1, 9:29 ampostingfilms

A master library of shorts

“i feel like we should always be making short vertical videos that can be posted anywhere. we keep a master directory of them all and iterate the quality. we keep track of what's been uploaded to which platforms”Kraig, Oct 1, 9:02 am

“we should also keep track of stats for each short video in the directory. snapshots added to their profiles so we can know which are successful and where.”Kraig, Oct 1, 9:06 am

• Every vertical clip: its source film, length, hook, route, audio and file in Drive. A new version sits beside the old one.
• Every place each clip is posted, with its numbers read about an hour, a day, three days, a week and a month after posting.
• It's a ledger: it never posts anything itself.

Oct 1, 5:27 pmsociallesson

Reply only when it helps

The first rule had every reply end with a link, so it replied too often and kept pushing the same guide.

“we need to just respond when it makes sense to respond we shouldn't respond to everything and we should only reply with the guide if they're looking for more information...”Kraig, Oct 1, 3:37 pm

• Only a real question it can answer gets a reply. Praise, stories, tags and emoji get none.
• A gear question gets that item's own link. A trip question gets the answer first, and the guide only if it covers more.
• At most one guide link per post a day, and never the same closing line twice.

What happened next: On Oct 5 it got each guide's key facts, so real route questions could be answered instead of held for me.

Oct 1, 9:39 pmfilmsposting

Every film, everywhere

“we need to make a log of where every long form video has been posted as well. since i want every piece of content i've made to be uploaded wherever it can go”Kraig, Oct 1, 8:24 pm

• Every upload of every film, on every platform, with the cut that went up.
• A gap list: which films are missing from which platforms, and what might stand in the way, like length limits, music or rights.
• The same schedule reads the numbers on film uploads too.

Oct 1, 9:56 pmroutine

A worker of my own

“yes let's build the chief of staff. i picture only testing the chief of staff with overnights for now”Kraig, Oct 1, 9:53 pm

• A scheduled Claude task on my Mac, hourly from 11pm to 6am, working through the to-do list of things Claude can finish alone.
• Only work I'd already approved. Nothing sent, published, paid, signed or deleted.
• Anything that needed me went into a morning summary.

Oct 2, 7:13 pmroutine

Every hour, and it finds its own work

“i know we have a lot of work to do and instead of me having to prompt it, can we have claude check what work to do every hour non-stop?”Kraig, Oct 2, 6:57 pm

“i think we should rebrand. chief of staff doesn't really describe what it is now. can we call it claude?”Kraig, Oct 2, 8:41 pm

• Every hour, day and night.
• When its list runs low, it files the next step of work I've already approved, quoting where I approved it, and does it.
• A cap on how much self-found work a run can take on.

Oct 2, 10:51 pmlesson

An idea lab, stopped after three days

“better yet, it should create more and keep them in a log and just organize them by what's best and then show me the best.”Kraig, Oct 2, 10:50 pm

“I feel like all of these are terrible... Like what the footage is matters less than the format. Like you're going in the wrong direction with all this. So let's just stop this whole like coming up with original ideas.”Kraig, Oct 5, 1:15 pm

• With time left in a run, the worker added original ideas to a ranked list and showed me the top three each morning.

What happened next: Stopped on Oct 5. The rule since: never pitch original ideas, only save mine.

Oct 3, 9:58 amroutinepace

Every 30 minutes, with work always ready

“not broken. we have no background work happening”Kraig, Oct 3, 9:54 am

“it seems like Claude gets pinged to work every 30 mins but sometimes the work only takes 4 minutes and then it sits there doing nothing until the next ping”Kraig, Oct 3, 10:07 pm

“i feel like we're burning through compute with claude running every 30 mins”Kraig, Oct 4, 8:02 pm

• The worker ran every 30 minutes and kept standing buffers of approved work full: films to review, short drafts, description previews, the next guide.
• Everything still stopped at my review.

What happened next: It used my plan's compute fast. On Oct 5 it dropped to four runs a day, and the pace kept changing for another week.

Oct 3, 3:25 pmpace

What each job costs

“if we know how much it costs to run this monthly and we can make that money back, it justifies the investment and we can start to scale it and improve it, make it more efficient.”Kraig, Oct 9, 9:09 am

• One small row for every AI call the workers make: which job, which model, how many tokens, and an estimated cost.
• A summary per job for today, the last week and the last month.
• Bookkeeping only: no job changed because of it.

What happened next: It showed that email triage cost far more than planned, which led to the cuts on Oct 11.

Oct 3, 10:39 pmsafety

A log of every sign-in

“So why can't this log live within the cloud...”Kraig, Oct 3, 9:49 pm

• Before any Claude session signs in somewhere, uses a code or changes an account setting, it writes down what it's about to do.
• The log lives in KraigOS, so every Claude session can read it.
• Never a password or a code: every line is cleaned first.

Oct 4, 6:02 pmsafety

The Trash rule

“well you can put things in the trash when it's safe to do so but i always empty the trash myself”Kraig, Oct 4, 6:02 pm

• Claude never deletes. A file that's safe to remove, like an exact copy already in Drive, goes to the Trash, and I empty it.

What happened next: On Oct 12 this became a standing job: when the Mac's free space drops too low, the oldest safe copies go to the Trash first.

Oct 5, 11:40 amsocial

Guide facts for real questions

Claude: Found that about half the comments held for me that week could have been answered from my guides, but the worker only saw the sales page.

• Each guide on sale publishes its key facts in its own words, dated. A comment matched to a guide gets that guide's facts, and only that guide's.
• Anything the facts don't clearly cover still comes to me.

What happened next: On Oct 8 a redesign of the guides page broke how the worker matched comments to guides, and every trip question came to me. The fix also made it stop and tell me if the page ever changes like that again.

Oct 5, 11:51 amposting

Formats as experiments

“what's most important is upgrading the formats and learning from these tests for future edits”Kraig, Oct 6, 8:46 am

• Every clip carries a format, like a map route, a story clip or a hook clip, and what it's testing.
• The report compares formats overall and per platform, so each post is a test.

Oct 6, 12:05 pmpace

Overnight, every 4 hours

“I feel like we can turn it up a little bit. And I also want it to run overnight.”Kraig, Oct 6, 12:04 pm

“I just want a continuous amount of work to be going. And that's based on like how much we have queued as well as how much we run the worker ping.”Kraig, Oct 6, 12:12 pm

• Six runs a day, every 4 hours around the clock.
• How much gets done is set by two dials: how much approved work is queued, and how often it runs.

Oct 7lessonroutine

A clock for the worker

Runs on a cheaper model quit after 30 to 40 seconds, said the work was already with another session, and logged durations that never happened.

• The worker moved to Opus and checks the real clock at the start and end of every run.
• “Blocked” has to name the reason.

Oct 7, 10:44 pmbuild

A timeline editor moves in

“just save the entire project in KraigOS and build the roadmap”Kraig, Oct 7, 10:43 pm

• A small video editor for my Mac, built for Claude's rough cuts, moved into the KraigOS code with its history.
• A roadmap, one step at a time with my OK. I still do the real edit in Final Cut.

Oct 8, 1:44 pmposting

A daily X post, in shadow

“I'll adjust the cadence and give you feedback on whether the posts were good or bad and how we can improve and iterate upon those.”Kraig, Oct 8, 1:39 pm

“the link would have to be there or the post like an image or the video like it it really isn't enough just to live as like random text you know”Kraig, Oct 8, 1:41 pm

• At most one post a day, and every post must carry a link, an image or a video.
• My OK covers the exact text and files; any edit takes it back. Posts that are too long, repeat or contain contact details are refused in code.
• It started in shadow, posting nothing.

What happened next: It was never connected. On Oct 12 it was switched off, and since Oct 13 X posts go out only to share a published article.

Oct 9, 7:05 pmposting

A ranked list of shorts

“We should always be trying to improve shorts and placing them in a list of best to worst based on how we think they'll perform.”Kraig, Oct 9, 7:05 pm

“it doesn't have to be a literal sheet. Like, I'm not going to ever look at it. It's for KraigOS to be able to read and use.”Kraig, Oct 9, 7:11 pm

• Every short ranked from best to worst, and posting goes from the top down.
• Later a score per platform: each clip against that platform's typical clip, from its first day, week and month.

Oct 10lesson

Read before you write

One run replaced a record's instructions with a one-line summary, and another wiped the notes on three clips.

• An update replaces a record's notes, so every change now reads the record first and writes the old text plus the new.

Oct 10, 11:39 pmpace

Burning compute

“let's switch claude worker to every 4 hours because i think we're burning compute too fast”Kraig, Oct 10, 10:12 am

“we're burning compute too fast. let's switch the claude worker to every 6 hours”Kraig, Oct 10, 3:36 pm

“let's run claude every 2 hours”Kraig, Oct 10, 11:39 pm

“i think we need to lower the work times because i'm losing compute too fast. maybe every 12 hours?”Kraig, Oct 11, 8:58 am

Claude: Added a usage check to the start of every run: near the plan's weekly limit, mechanical work moves to a cheaper model, and close to it only urgent items run.

• The schedule changed six times in three days, from every 2 hours to every 12 and back.
• Choosing the pace stays my call; Claude watches the week's usage and suggests a change when it's off.

(open full size)

Oct 11, 2:14 pmdesign

Three kinds of work

“i think we need to organize what work or items are one and done, done but can be updated or work that is non-stop always happening”Kraig, Oct 11, 1:35 pm

• One-off work closes when it's done. Living work closes but comes back for a refresh after 90 days. Ongoing work has a cadence and a one-line health check.
• My list leaves out ongoing work that's on track.

Oct 11, 8:01 pmpostinglesson

Facebook goes back to native

Reels published through the API reached far fewer people than the ones I posted myself.

“i don't like this workflow. we'll just have you put events on my cal about when to post what where and i'll have you control my phone and do it then”Kraig, Oct 11, 8:01 pm

• Facebook posts are never made through the API again. Each one becomes a calendar event with its file ready, posted natively from my phone.

What happened next: On Oct 13 KraigOS started doing that phone step itself.

Oct 11, 11:23 pmpaceemail

Cutting the email bill

A week of cost rows showed email triage running at about four times its monthly target, and social replies costing too much per posted reply.

“Yes go”Kraig, Oct 11, 10:43 pm

• Sorting email moved to a cheaper model; replies stayed on the best one.
• A free check in plain code archives unmistakable bulk mail before any AI sees it.
• Social replies moved from the cloud worker to the Claude task on my Mac.

What happened next: The next day the whole email job moved to a Claude routine, with no AI calls left on Cloudflare.

Oct 12, 9:14 amroutine

Auto Claude

“i picture having an "auto Claude" that runs every hour. it should try to do everything i would be doing and whatever it can. Basically instead of my having to prompt in claude, every hour it tries to be me and get work done better than i even could.”Kraig, Oct 12, 9:14 am

“i want to get back into a review period. i want to review most everything, especially email before you move forward. i want to trust that your next step on auto is actually correct.”Kraig, Oct 12, 9:17 am

“this new auto claude is replacing that old routine. let's stop the old one.”Kraig, Oct 12, 9:18 am

Claude: Designed two routines: one in the cloud every hour for connector work, one on my Mac every 4 hours for files and my signed-in browser. Each part of the work belongs to exactly one, and both write to one review list.

• Every run starts by reading two records: the modes (what each part may do on its own) and the lessons (my corrections so far).
• Most parts start in review: the routine proposes, and nothing happens until I answer.
• The old Mac worker was switched off that morning.

Oct 12, 9:34 amcalendar

My calendar is a dashboard

“i don't want to have to ever actually type in my cal. i might reference it on my phone time to time but i'll usually interface the cal through claude chats here.”Kraig, Oct 12, 9:34 am

“cal is less risk so that's why it's enabled to be on auto pilot now”Kraig, Oct 12, 9:35 am

“i also like to say "morning" when i start my work in claude so that also might be a good time/place to update me and get started”Kraig, Oct 12, 10:08 am

• The calendar is on autopilot from day one: the routine adds, moves and removes events from the records.
• A short daily brief goes on the calendar each morning.
• When I say “morning” in a chat, Claude tells me what needs me and walks me through the review list.

Oct 12, 10:05 amroutinelesson

Reading less before working

“claude should maintain this going forward as well. i picture this right now is a one time clean up but it might get bad again in a week or month so we need to fix this problem once and for all right?”Kraig, Oct 12, 10:05 am

Claude: Measured it: every run read about 24,000 words of rules and notes before doing any work.

• A brief of about 1,500 words, one short note per part of the work, and the dated history moved to its own file.
• Word budgets for every file, with a check that warns when one grows past its budget.

Oct 12, 10:10 ampace

Compute is Claude's job

“this should all be managed by claude. i don't want to have to worry about this. claude can do it better than i ever could as well. help me do better work for less money. claude should help me do this all efficiently. i don't want to waste money or compute”Kraig, Oct 12, 10:10 am

• Claude sets how often the routines run so the week's work fits my plan, and says so when the pace is off.

Oct 12, 10:49 amlesson

A list that holds only decisions

The first review list was full of record housekeeping that only looked like decisions.

“I see all of these. I don't know, fully understand what you're waiting for me to decide here now. Like, what am I reviewing?”Kraig, Oct 12, 10:49 am

• Record housekeeping became Claude's job, on autopilot.
• The review list holds only real decisions: trade-offs, anything sent or public, or something only I know.
• Every no or change I give becomes a short lesson that every run reads first.

Oct 12, 6:54 pmemail

Sending paused, archiving back

“i want to put a pause on auto reply or auto archive all emails for now”Kraig, Oct 12, 9:09 am

“We need to start archiving emails out of inbox once they're done”Kraig, Oct 12, 6:54 pm

• No automatic replies. A reply is a draft on my list, sent from my main chat after my yes on the exact text.
• Archiving came back that evening on autopilot, but only for threads that are fully done, each listed so I can pull it back.
• That night the inbox reached zero.

Oct 12, 9:44 pmroutine

A disk that stays clear

“it seems like it's been doing a bad job of getting rid of files that we might not need anymore. over 300gbs is huge”Kraig, Oct 12, 9:44 pm

• Every Mac run checks free space. Below a floor, the oldest safe copies go to the Trash first, never an only copy.
• A hard floor no download, render or copy may cross. Each move is listed in the report.

What happened next: The first pass took the Mac from 19 GB free to 288 GB.

Oct 12, 10:15 pmsocial

Guide facts for every session

The cloud routine couldn't reach my website, so a fan's trip question had been parked for me.

“you can just do them all now. i can deploy 2 once it's ready”Kraig, Oct 12, 9:59 pm

• A read-only tool gives any Claude session the guides on sale and one guide's key facts, marked as outside data.

Oct 12, 10:25 pmbuild

A page about KraigOS

“i'm considering having a dedicated page on the website for KraigOS so people can understand what i've built, what i'm using and how they could make their own version and why”Kraig, Oct 12, 10:25 pm

• A living page on this site: what KraigOS is, why I built it, what it does, what I use and how to build your own. It changes as KraigOS does.

Oct 13, 1:39 pmroutine

One routine, not two

“Yeah, let's completely fold the Auto Claude cloud into our Auto Claude local and stop using Auto Claude cloud.”Kraig, Oct 13, 1:39 pm

• The cloud routine was switched off. The Mac routine does both halves' jobs in one run: email, calendar, records and pitches first, then files, Drive and the rest.

What happened next: A single routine means one set of instructions to keep current, and no two routines stepping on the same item.

Oct 13, 1:43 pmroutinedesign

Earning autopilot

“Yeah, let's set it up this way.”Kraig, Oct 13, 1:43 pm

Claude: Replaced a one-time scorecard with a running track record for each part of the work.

• Every item on my list says what the routine would do on its own, and my answer is logged as agreed, changed or wrong.
• A part that matches my answers 15 times in a row gets a card asking to move to autopilot. Only my yes moves it.
• One real mistake on autopilot puts a part back in review.

(open full size)

Oct 13, 3:10 pmpostingroutine

Shorts on autopilot

“try to automate all of this”Kraig, Oct 13, 2:59 pm

“you can include YouTube shorts on auto with tiktok and facebook”Kraig, Oct 13, 3:00 pm

• Seven days of shorts stay queued, one post a day on each of TikTok, YouTube Shorts and Facebook.
• Only clips I've already approved, from the top of the ranked list down, never the same clip twice on one platform.
• New clips and new formats still come to me first. Instagram stays manual.

Oct 13, 5:36 pmpaceroutine

Every 2 hours

“let's run KraigOS every 2 hours”Kraig, Oct 13, 5:35 pm

• The routine runs every 2 hours, around the clock, while my Mac is awake.
• Each run re-checks every open item on my list against what's already been done in my main chat, so nothing handled is raised twice.

Oct 13, 7:19 pmfilmsbuild

A music library

“It might be interesting to keep a running list of every single song that we've ever licensed with which platform and for which video. It would just be helpful to have that information in the database so that we can use that to find similar music or to know if we have already used a song or if we want to reuse a song.”Kraig, Oct 13, 12:55 pm

“Yeah, that looks good. You can build it.”Kraig, Oct 13, 12:57 pm

“3 yes”Kraig, Oct 13, 7:18 pm

Claude: Built it that afternoon and filled it from what was already on record: licences, downloads, notes and the songs credited on my films.

• Every song I've licensed and every place it's used, in a film, a clip or anything else.
• Search by mood and tags, find similar songs, see what's never been used, and track any claim on a use until it's cleared.
• A ledger: it never licenses, buys or downloads anything.

What happened next: Live that evening, with more than 800 songs.

Oct 13, 8:16 pmpostingroutine

Posting from my phone

“Yes from phone.”Kraig, Oct 13, 8:16 pm

• Each afternoon the routine posts the day's approved Facebook reel natively from my phone, through iPhone Mirroring on the Mac, then checks it's live.
• If the phone is locked or mirroring isn't available, the reel stays on my list. A clip I haven't approved is never posted.

Oct 14, 4:35 pmbuild

This devlog

I'd just seen the same kind of devlog built for a game I'm making with Claude.

“i also want a full dev log like this game but for KraigOS development.”Kraig, Oct 14, 4:35 pm

Claude: Wrote it from the code history, the rule files and my own messages, and drew the diagrams. It's about how the system works, never the business it runs.

• Every entry has a date, and my own words wherever I have them.
• It's updated as KraigOS changes.