How to use Microsoft Scout to rebuild a blog
Microsoft Scout rebuilt a WordPress blog through browser and REST actions. Human review caught a missing class and preserved permalinks during category cleanup.
iiu.dk
Original prompt
Shared by the source author. See source notes for context.
no twitter, I don’t use it anymore, strip it everywhere.
Reach people exploring AI agents
See placements →What happened
The WordPress rebuild shipped after visual review and accessibility/performance checks. The News slug was retained to preserve existing permalinks; cost and time savings were estimated.
Reported by Jens Kofod — Personal blogHow the agent did it
- Scout drove the browser and used workspace files and WordPress REST calls to implement the rebuild.
- Kofod corrected design choices and preserved the News parent slug to retain existing permalinks.
- Human approvals, backups and visual review accompanied accessibility and performance checks before publication.
Where a person stepped in
Kofod made design decisions, read publishing diffs, required production backups and approved destructive API changes; visual review and permalink decisions stayed human.
Jens Kofod used a browser-capable Microsoft agent to rebuild his WordPress blog. The original account names the internal tool Clawpilot; a follow-up by the same author explicitly identifies Microsoft Scout as the agent used for that rebuild.
The agent drove Edge, read and wrote workspace files and used the WordPress REST API for direct changes. It built a block theme, reorganized category filters, revised the About page and added structured metadata. Kofod corrected brand choices through short instructions, including removing unwanted social metadata.
Two misses required human judgment. The agent styled a button with a nonexistent theme class, which visual review caught. It also proposed deleting the News category, threatening existing permalinks; Kofod retained the parent slug and emptied the category instead. Production edits required backups, destructive REST calls required confirmation and publication required reading the diff.
The site shipped with accessibility and performance checks using axe-core, Pa11y and Lighthouse. Those checks complemented visual review rather than finding every design mistake. Kofod's reported cost and time comparison was estimated, so it is not treated as measured savings. The result is a real published rebuild with specific preservation and approval decisions around an agent executing the work.
Prompt
Original prompt
Source: Personal blog · Jens Kofod
Frequently asked questions
Why is the agent called Scout here?
The same author's follow-up explicitly identifies Scout as the agent used for the Clawpilot-named rebuild.
What would deleting News have broken?
Existing post permalinks tied to the category's parent slug.
Were saved hours measured?
No. The author's cost and solo-work comparisons were estimates.
More details
About this account
Scout drove the browser and used workspace files and WordPress REST calls to implement the rebuild. Kofod corrected design choices and preserved the News parent slug to retain existing permalinks.
Original and same-author follow-up opened. Original calls the internal agent Clawpilot; follow-up explicitly calls this project Microsoft Scout. Kofod is a Microsoft employee. Cost and saved-time figures were estimates, not measured savings. Original prompt excerpt.
Credit: Jens Kofod — Personal blog
Source published 1 Jun 2026
Source checked 14 Oct 2026
Tools and topics
Microsoft Scout · Microsoft Edge · WordPress REST API · axe-core · Pa11y · Lighthouse
WordPress rebuild · Permalink preservation
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.