Jun Sasaki / Log

2026-03-14

The story of wanting to create an AI shadow clone.

What do I want to do, you ask? Simply put, it's about AI agents.

I decided to start keeping a log after reading an article about a CTO at some company in America who is creating a clone of himself.
Even before that, I realized that as I get older, I completely forget what I was thinking and how I acted just three months later.
Wait a minute.
I don't even remember what happened a day ago.
At the very least, I've started to struggle with matching faces to names. I used to remember them instantly when I was in my 20s.
Oh boy, I've really become an old man.

Forming a personality from logs

Since OpenCrow started becoming popular, I've been wondering how to make an AI agent act like my own personality while having it handle things I currently do, like replying to emails and various other tasks.
According to that CTO, he has a base built by digging up all his past emails, media appearances, and everything else to feed it information.
Wait a minute.
If it were someone like Ohtani, information would be scattered everywhere, but as an ordinary citizen, I have to create the information to provide myself.
That's it, I'll start keeping logs.

I'm going to make it a systematic process.

If the premise is to "create a database," you need a proper system. I built a Next.js site using Obsidian and git, managed the data with Supabase, and even added billing functionality with Stripe.
I built my own business log site, log.sassamahha.me, from scratch.
That said, I just churned it out with Cursor.

In practice, the system is convenient.
I can manage metadata with front matter, and I can use git for version control. I think it was an ideal configuration for engineer-led management.

However, there was a fundamental problem for me.

I just don't go out of my way to sit at my PC...

Obsidian and git are both PC-based systems. The moment I have to think "should I write today's entry?", open my Mac, and type in the terminal, I've already lost the motivation to continue.
It was fun to build, but operating it was a different story.
As always, I forgot about my own personality.
Designing with the assumption that this motivation won't last is the prerequisite.

So, I decided to use note.
I'm complaining even though I'm using it, but the UI is cluttered and I keep thinking "make an API already," but for now, the fact that I can complete everything on a smartphone app is a higher priority.
(To be precise, sharing to X can only be done on the web version, so I have a shortcut icon on my smartphone.)

Furthermore, I don't really write diaries in the first place, and I close my PC when I'm done, so I've started to think it might be fine to just leave logs at a level where I tell Claude to "summarize this" after I finish some work.
If I do that, I can just copy and paste to post. It can be messy.
I apologize for the article not being intended for readers, but since I'm not writing it with the premise of having people read it anyway, it's no problem.

The only thing is that I think the feature on note where articles become free via X reposts is worth using; I'll set it to paid, and have people who want to spread it retweet it.
By doing that, I can vent my poison as I please. I can mess around. You can't do this if it's free. My public persona is surprisingly well-behaved. (A truly undesirable, vain personality)
I couldn't do this on my own site because it requires expensive fees to X, so I should borrow the power of platforms where I should.

Towards a shadow clone

Well, the title has gone completely off-track, but I haven't abandoned the idea of turning it into a database.
note has an XML export feature, so I'm thinking I can just extract the articles in bulk when they accumulate and feed them into something like notebookLM.
I haven't thought about the detailed specifications yet. For now, the top priority is how to keep logging going thinly and for a long time.

It feels a bit uncomfortable to entrust master data to note, but I think a "messy system that continues" is 100 times better than a "perfect system that doesn't."

Advertisement