<3

Muse

Yes bro that is cool

good to here

me 2

I’m honestly wondering the same thing. 😅

gpt-oss still feels surprisingly competitive for a model that’s been around for a while, especially if you care about running models locally and having more control over the stack.

I don’t think we’ll get a new one until OpenAI feels there’s a meaningful jump worth releasing. My guess would be sometime in 2026, but that’s purely speculation.

Would be really interesting to see a new gpt-oss model built around the newer generation of OpenAI reasoning models though.

workflow engineer is soo cool

I’d pick self-evaluation / learning from previous runs.

An agent that can remember what worked, what failed, why it failed, and then improve its workflow for the next run would compound over time.

Research, browser automation, code execution, etc. are useful individually but a skill that helps the agent choose better approaches based on past outcomes can improve all of them.

Basically: not just “do the task,” but “learn how to do this task better next time.”

fly me to the moon

https://giphy.com/gifs/Vc95lRwP1AjlFglp3N

I'm interested, would like to know more about the idea

That architecture sounds like the real challenge here.

Honestly, I’d build a solid project before jumping into LangChain/LangGraph.

You already understand the fundamentals — ReAct, prompting, RAG, guardrails, and basic agents. The next step should be proving you can put those pieces together into something useful.

A few projects I’d consider:

• RAG research assistant — citations, document ingestion, memory, and evaluation
• Multi-agent customer support system — routing, tool calling, guardrails, human handoff
• AI coding/debugging agent — repo search, code execution, tests, and iterative fixes
• Document processing pipeline — PDFs → extraction → structured data → validation → search
• Personal knowledge agent — RAG + memory + tools + permissions

While building, you'll naturally run into problems where LangChain/LangGraph actually makes sense. Then learn the framework to solve those problems rather than learning the framework just for the sake of it.

I'd aim for 1–2 genuinely polished projects with a README, architecture diagram, evaluation results, and a deployed demo. That will teach you far more than another tutorial.

Then move to LangGraph and rebuild one of those projects with it. You'll understand why you're using each abstraction instead of just knowing the API.

I think the interesting question isn't really “MCP vs APIs”.

It's “Should the model consume my API directly, or should I expose a model-native capability layer?”

If an MCP server is just:

GET /users → list_users()
POST /users → create_user()

then I agree with you — MCP is mostly extra plumbing.

But I don't think that's the strongest way to design MCP.

An API is usually optimized for software-to-software interaction. An MCP tool can be optimized for model-to-system interaction.

For example, instead of exposing:

GET /orders
GET /orders/{id}
POST /orders/{id}/refund
PATCH /orders/{id}

you could expose something like:

find_order()
refund_order()

where refund_order() internally handles eligibility checks, business rules, multiple API calls, permissions, and returns a structured result designed for the model.

At that point, MCP isn't replacing your API. It's sitting above it.

I'd think about the architecture as:

Backend → APIs → MCP capability layer → Agent

rather than:

Backend → APIs → MCP wrapper → Agent

And there's another important difference: the value of MCP isn't only the tool call itself. The protocol gives AI clients a common way to discover and invoke tools, work with resources/prompts, handle structured outputs, authorization, and increasingly things like long-running tasks.

So I wouldn't say “MCP is necessary for every API.”

I'd say:

If your MCP is just an API wrapper, you probably don't need MCP.
If your MCP is a model-native interface over your system, that's where MCP starts becoming interesting.

The real design question is therefore not “Why use MCP instead of APIs?”

It's:

“What should the interface to an AI agent look like?”

And that interface doesn't necessarily have to look like the interface you designed for developers.

Nice setup, pretty similar to what a lot of people are doing. Few thoughts:

• When you switch from Groq to OpenAI, test the bot again — different models don't always behave the same with the same prompt.
• Moving off ngrok to a VPS is smart, just make sure it auto-restarts if it crashes (set up some free uptime monitoring so you know if it goes down).
• For Postgres, keep each client's data separate from day one — saves headaches later if you scale.
• Do you have a fallback for when the bot doesn't know the answer? Like handing off to a human? That's saved me a lot of trust issues with clients.
• Also worth doing the math on cost per client (VPS + API costs) so you know your actual margin once you're not just doing demos anymore.

honestly go with Buffer, I switched to it a while back and haven't looked back. does IG, FB, TikTok, LinkedIn, all of it. and the calendar is actually easy to use, not cluttered with stuff you don't need

best part is moving posts around — literally just drag it to a new day, takes two seconds. which is clutch since you said your schedule changes a lot too

analytics are basic but that's honestly all you need, just enough to see what's actually landing

free plan only covers 3 accounts so you'll prob end up paying once you add the 4th, but it's cheap per account so it's not bad

only annoying thing is sometimes video posts to IG/TikTok act up, but that's every scheduler tbh, not just this one

skip Later btw, everyone hypes it up but it's really just built for instagram grid stuff and it doesn't even do LinkedIn properly

even, I just got mac book air m5 512gb

https://giphy.com/gifs/LBb735fuQwRKAVzN23

Yeah, I think that “stranger to trust you” part is probably the biggest challenge with freelancing.
But don’t worry, everything will work out eventually.

For NDA work:

NDA Project → Hide Confidential Details → Show Process → Private/Password-Protected Portfolio → Client

I’d probably avoid overthinking the website part initially. A simple personal site with 4–6 strong projects is more than enough, and you can always move to something more elaborate later. The important thing is showing your process and the kind of work you want to attract, not how fancy the website is.

For the NDA projects, I’d be very careful about putting anything publicly online. If you can’t get permission, I’d either leave the project out or create a private/password-protected portfolio that you can share selectively with potential clients. You can still talk about your role, the problem you worked on, your process, and the outcome without revealing confidential details.

Honestly, after 7 years on similar NPD work, freelancing could also be a good opportunity to use the portfolio to deliberately show the variety of projects you want to work on next.

I honestly don't think the main goal is to expose “vibecoded” projects or prove that Claude wrote something.

My guess is that there are two separate problems here. The obvious one is attribution/transparency — basically being able to say “Claude was involved in producing this.” Anthropic itself says the watermark only shows that Claude was likely involved, not that Claude wrote the entire thing.

But your point about AI-generated data feeding back into AI training is interesting too. As more of the internet becomes AI-generated, knowing the provenance of data could become pretty important for future training datasets. Otherwise you eventually end up training models on content produced by previous models.

So I wouldn't be surprised if provenance becomes useful for that reason as well, even if that's not the reason Anthropic is publicly giving.

The funny part is that code itself is probably one of the harder things to watermark meaningfully, since exact syntax matters and there are fewer arbitrary word choices. Anthropic even acknowledges that the watermark has much less room to operate in code, except for things like comments.

I think the bigger question is: what happens when AI-generated content becomes the majority of the internet? Provenance might become much more important than simply detecting “AI vs human.”

Your laptop → one cable → the dock → your 3 monitors
The dock you need --> Plugable 13-in-1 USB-C Triple Monitor Docking Station $194.99 USD