md2wechat 2.0.5: Building a Real Confirmation Layer Before Publishing

md2wechat 2.0.5 is now out.

The most important change in this release is not a bigger command list. It is that the product now has a more explicit confirmation layer.

If I had to summarize this version in one sentence, it would be this:

This is not a feature-stacking release. It is a release that makes the system less misleading and more trustworthy.

Screenshot: 2.0.5 release cover

What problem does 2.0.5 actually solve

If you use AI to help write or format WeChat articles, the pain points are usually familiar:

• the assistant says the article is ready, but the result in WeChat is not what you thought it would be
• local images look fine, but something breaks when the draft is created
• there are many themes, but you still cannot tell which one the system will actually use
• the failure message points you in the wrong direction

These may look like separate issues, but they share one root cause:

you cannot see how the system understands the content, and you cannot see the likely final result before publishing.

That is why 2.0.5 matters.
The release is really about adding a missing confirmation layer.

The four changes that matter most

I would reduce this release to four core changes.

1. inspect was added

inspect does one very practical job:

before conversion, upload, or draft creation, it tells you how the system is going to interpret the article.

That includes signals such as:

• which line becomes the final title
• where the author and summary come from
• whether an H1 will be duplicated in the body
• whether the article is actually ready for draft creation

The command is straightforward:

md2wechat inspect article.md --json

The value here is not just one extra command.
The value is that users can finally verify the interpretation before execution.

Many problems used to appear only after publishing.
Now the system can expose them earlier.

2. preview was added

If inspect answers "how will the system interpret this article," then preview answers "what will this look like."

md2wechat preview article.md

It gives you a local preview so you can inspect the output in the browser first.

Two changes matter here:

• in API mode, it can produce a real preview
• in AI mode, it no longer pretends to be the final result

That matters more than it sounds.

The most dangerous kind of product behavior is often something that looks like the final output but is not actually the final output.

So this release makes a deliberate choice:

it is better to be honest about the current state than to fake a polished result.

3. Machine-readable output is cleaner now

Besides the human-facing confirmation layer, this release also tightens machine-facing behavior.

Some of the most important fixes are:

• --json now keeps stdout as pure JSON
• convert --preview now emits pure HTML
• machine-readable flows no longer mix in unrelated banners or prompts

That makes a real difference for scripts, automation, and agents.

It means the surrounding workflow no longer has to clean up the output before using it.

These changes are not flashy, but they matter a lot once the tool becomes part of a larger pipeline.

4. Error guidance, docs, skill entry points, and release checks were recalibrated

Another large part of this release lives in places that do not look like "new features."

One practical example is the WeChat error 45004.

It used to be easy to misread that error as a body-length problem.
In practice, the better first checks are often:

• digest
• summary
• description

That kind of correction matters because it reduces false diagnosis.

This release also realigns:

• documentation
• skill entry guidance
• release checks
• version anchors
• error explanations

The goal is simple:

make the docs, the agent guidance, and the runtime behavior describe the same reality.

The core flow is much clearer now

After 2.0.5, the main path can be reduced to:

inspect -> preview -> convert / upload / draft

In plain terms:

1. inspect first
2. preview next
3. publish last

That does not just make the workflow longer. It makes it safer.

The important difference is that confirmation and execution are no longer blurred together.

Users do not have to gamble on the result and fix things afterward.
They can confirm first and then decide whether to continue.

Why the confirmation layer matters so much

I keep coming back to one belief:

the hardest part of AI tools is not whether they can do something, but whether they mislead you while doing it.

A system can have many features and still feel unsafe if the confirmation layer and execution layer do not match.

That is when users start losing trust:

• the interpretation may not match the intent
• the output may not match what the UI suggests
• the error may not point to the real issue

That is why I see 2.0.5 as more important than a typical small release.

It addresses trust, not just capability count.

What I have already verified in a real flow

This release was not treated as a docs-only update.

The core flow was verified in a real environment, including:

• local image upload
• image replacement back into the article
• preview flow
• draft creation

So the main chain is not just theoretically cleaner. It has been exercised end to end.

Who benefits most from this release

This update should be most useful if you are in one of these groups:

• you write WeChat articles in Markdown
• you ask AI to help write WeChat articles
• you connect md2wechat into an agent workflow
• you want writing, formatting, and draft publishing to behave like one process

What those users usually need is not another command.
They need answers to a few basic questions:

• how will the system interpret this content
• what will it look like before publishing
• how can I reduce misfires and rework

That is exactly what 2.0.5 improves.

More advanced themes and modules are coming next

Now that the confirmation layer is in place, the next direction is improving the publishing surface itself.

The next wave of work is expected to include:

• cover cards
• data cards
• comparison modules
• step-flow sections

These are more useful for real-world materials such as:

• brand announcements
• sales proposals
• product explainers

So the next step is not only "can it publish," but also "can it feel closer to polished business content."

Closing

For me, md2wechat 2.0.5 is not a release that merely adds a few parameters.

It is a release that tightens the publishing loop.

The biggest shift is simple:

the system is more honest now, and much easier to confirm before acting.

If you are already using Markdown and agents for WeChat writing, this version should feel noticeably smoother.

Project: github.com/geekjourneyx/md2wechat-skill

Original WeChat article: md2wechat 2.0.5 release