Day 16 building my AI agent — this one isn’t pretty

[UPDATE] Day 16 building my AI agent — this one isn’t pretty

Original post:
I built a personal AI agent because I'm a chronic procrastinator — 7 days of building, here's what I learned.

Quick recap:
I’m building a personal AI agent to help with procrastination — something that doesn’t just remind you, but actually keeps you accountable.

I wish I could say everything is going great.

That I figured it all out.

That the system is working exactly how I imagined.

But the truth is — the last 6–7 days have been chaotic.

I spent 2 full days just thinking about architecture.

Trying to break down:

• what I want this system to do
• vs what I’m actually capable of building

And the gap between those two is… uncomfortable.

I’m not a developer.
I’m definitely not an ML engineer.

And trying to design something this complex without that background basically fried my brain.

Then comes the ironic part.

Right in the middle of all this, I had an appointment with a psychiatrist.

And somehow, the guy trying to build an AI to help people stay consistent and disciplined…

…got diagnosed with ADHD, bipolar disorder, and anxiety.

Yeah.

Feels almost hypocritical.

Or maybe it explains everything.

Days 5 and 6?

Back to architecture.

Still stuck.

Still overthinking.

Still trying to figure out how to make something that:

• understands the user without being annoying
• knows when to push and when to back off
• actually feels like a “second brain” instead of a nagging app

That’s not easy.

Not even close.

At some point, I reached out to the Machine Learning community.

That helped.

Not because they gave me the answer — but because it forced me to think more openly.

Still, I caught myself procrastinating too.

Not because I didn’t want to work.

But because I didn’t know what the right thing to build next was.

Where I am now:

I’m close to an architecture that makes sense (at least in my head).

The agent is starting to work in some real scenarios.

Example:

In workout tracking, I can just open the chat and say what I did — no structure, no commands — and it interprets and logs it surprisingly well.

That part is actually working.

But the core problem is still there:

It’s still reactive.

And what I want is something truly proactive.

Something that:

• anticipates
• nudges at the right time
• adapts without being overwhelming

And that’s way harder than I thought.

The real point of this post:

This is not easy.

This is not:
“build something in a no-code tool and become a millionaire overnight”

It’s messy.

It’s frustrating.

It’s a lot of doubt, a lot of second-guessing, and a lot of hitting walls.

And honestly?

These moments are probably the real test.

Not the hype.
Not the idea.
Not the first version.

But whether you keep going when things stop making sense.

A lot of people would’ve quit already.

I won’t.

I’ve spent too much time thinking about this, rebuilding it, breaking it again.

I’m not stopping here.

I just hope the next update is different.

I hope I can come back and say:

“I finally built an architecture that works.
Something that actually thinks.
Something that feels right.”

if you can criticize, comment on the ideas, or even roast me I’d really appreciate it — all feedback is valuable
:::