If I'm being honest, I'm online (and on PC in general) more than is healthy. Never less than 12 to 14 hours a day.

In practice, I use it most often for:

creating graphics

I just fixed and rebuilt an entire AI automation flow without opening the flow editor once.
Here's what happened:
We have a YouTube script generation pipeline on Serenities. It takes a keyword (or YouTube URLs), generates  an outline, then writes each section with precise word counts. Two branches one for URLs, one for direct topics.
The URL branch was broken. Not obviously broken. Subtly broken it was jumping straight from transcript cleansing to a single Claude call with no outline step, no section iteration, no word count targeting. Just a raw prompt that guessed at length every time.
I asked Claude to check it via MCP.
Within seconds it had read the entire flow every node, every edge, every config. It found:
- A broken template variable resolving to [undefined] instead of the word count
- Extended thinking enabled on a cleansing node (pointless, just burning tokens)
- The URL branch missing 7 nodes that the keyword branch had
- The MCP help guide serving 5 thin topics with almost no real documentation
Then still without me touching the UI it:
Added 7 new nodes to the URL branch (outline prompt, Claude outline generate, JSON cleaner, iterator,
section prompt, section writer, text aggregator)
Rewired all the edges correctly
Updated the webhook response to pull from the new pipeline
Rewrote all 5 MCP help topics with complete documentation utility node configs, template variable syntax,
Claude toolInputJson templates, debugging guides, everything
One conversation. Zero UI clicks. The flow went from broken to production-ready.
This is what MCP actually unlocks. Not just "ask AI to explain your code." Ask AI to read your live
infrastructure, reason about what's wrong, and fix it programmatically, precisely, at the API level.
We built MCP support into Serenities so AI agents can build and manage flows on behalf of users. Today I used
it on our own platform. It worked exactly as intended.
The future of automation isn't drag-and-drop. It's conversational.

After launching Sway on Product Hunt, we read every single comment.

Some of you were excited. Some curious. Some skeptical. That was good.
Because Sway is built for reflective thinking and that starts with us.

Here s what we changed based on your feedback:

Today I received a question about proper launch preparation:

Nika, how long should this take us?

And I didn t have a clear answer.

First of all, I want to thank you for voting for us in yesterday's launch - you still can, the week is not over. HERE

Second thing, I summarised some things that I realised, reflected on, and maybe should have known sooner:

Many people were looking for an answer in one category, namely, Forums Streaks.

This metric by itself only tells you that people log in to the app.

Every feed today claims to be better curated or more relevant.
But most of them still measure success by how long you stay.

I ve caught myself opening Twitter or YouTube to check one specific thing, then resurfacing 30 45 minutes later,

wondering where the time went.

Curious how this plays out for others here.
When you open a feed for a quick check, how long do you actually stay?
And does it usually feel worth it after?

If you use an Apple Watch, let s talk about the complications we actually use every day.

I ll start with the one I check the most.
For me, it s the Day and Night complication from Weather mini.