ArcaneMoose

> You need a high-level, far-away map of the entire system, and you need to know just enough to know where you need to dive in

One thing that puts me squarely in the Optimist camp is that such a map can often be created by AI just-in-time. Sure you might not know every detail of what it said, but you can simply follow up and build your understanding.

Really cool but should limit # of people shown when there are too many. Currently it gets really laggy

I recently started interacting with JIRA exclusively through AI agents (as a Skill in Cursor) and the difference between Linear and JIRA has immediately evaporated. No UI clunkiness problems if I don't even use it :)

More scenarios:

- AI generated VFX on top of non-AI video

- AI upscaling of low res footage

- AI frame interpolation for synthetic slow-mo

- Modified / composited AI video

- Footage created by "Extend Scene" features in Premiere Pro and others

- Word correction from tools like Descript

- AI relighting or colorization

- Reaction video to a video containing AI-generated content

And in general, what amount of combination of any of these applications constitutes as "AI generated"? If I have a 30 minute video with a 3 second AI generated clip, do I get the same label as full-blown AI slop video?

I absolutely hate those full-blown AI 'explainers' that just have AI voiceover and a bunch of auto-placed b-roll. I don't want to see them. But I don't think that falls in the same bucket as a creative short film with some AI-generated SFX or someone doing a tutorial with an AI-generated lofi track in the background.

I'm curious where the line is.. several ambiguous but common scenarios:

- Occasional AI b-roll during explainer videos

- AI generated backing track (music)

- AI generated shots sprinkled in a short film

- Showing examples of AI video as an AI capability update or commentary

I still think MCP is completely unnecessary (and have from the start). The article correctly points out where CLI > MCP but stops short on 2 points:

1. Documenting the interface without MCP. This problem is best solved by the use of Skills which can contain instructions for both CLIs and APIs (or any other integration). Agents only load the relevant details when needed. This also makes it easy to customize the docs for the specific cases you are working with and build skills that use a subset of the tools.

2. Regarding all of the centralization benefits attributed to remote MCPs - you can get the same benefits with a traditional centralized proxy as well. MCP doesn't inherently grant you any of those benefits. If I use AWS sso via CLI, boom all of my permissions are tied to my account, benefit from central management, and have all the observability benefits.

In my mind, use Skills to document what to do and benefit from targeted progressive disclosure, and use CLIs and REST APIs for the actual interaction with services.

Beautiful work!

I was surprised by my own feelings at the end of the post. I kind of felt bad for the AI being "put down" in a weird way? Kinda like the feeling you get when you see a robot dog get kicked. Regardless, this has been a fun series to follow - thanks for sharing!

Extensions have too many security risks for me. At this point I'd rather just vibe code my own extension than trust something with so much access and unpredictable ownership.

Great write-up! Thanks for sharing your journey

This model is awesome. I am building an infinite CYOA game and this was a drop-in replacement for my scene image generation. Faster, cheaper, and higher quality than what I was using before!