SEO agent
What the SEO agent crawls each week, what it reads from Search Console and the link profile, and how its fixes arrive as pull requests.
What it does
The SEO agent rebuilds your site snapshot every week and audits the site against it: what the crawl found, what Search Console says, what the link profile says, and what moved since last week.
It does not write the fixes itself. The crawl leaves recommendations, and separate fix runs turn the most urgent ones into draft pull requests on the repository that serves the pages.
When it runs
Weekly. It is on as soon as the product has a Site surface, since an audit publishes nothing. The cadence comes from the agent and is not editable, and it has no weekly cap. After each audit, up to five fix runs start on the most urgent open recommendations that have no pull request yet.
What it needs
The GitHub connector, and a Site surface. The reason is plain: a page is fixed by a pull request on the repository that serves it, so without the repository connected the agent has nothing to leave you and does not run. Search Console is not required — the audit runs with or without Google, and reads it when the property is bound.
What it reads
The foundation doc, the growth plan and the product memory first. Then the site.
- The site snapshot, rebuilt that day: robots.txt, the sitemaps, the pages with their titles, meta descriptions, headings, canonicals, Open Graph, structured data and links, plus the files at the root of the site.
- The recommendations already open, so a page that no longer has the problem is closed rather than reported again.
- Search Console over the last 30 days when the property is bound, ranking drops included.
- The link profile, refreshed the same week from the market index: the referring domains, what was gained and lost over thirty days, and the anchor text those links say.
What it leaves you
No proposals. It leaves recommendations: one per problem, on a page or on the site itself, rated critical or warning and kept from one crawl to the next. The fix runs that follow open one draft pull request each; you approve a recommendation by merging its pull request, or dismiss it for good. Core Web Vitals go to the journal rather than into the queue.
The skills it runs
It enters through seo-audit, and may activate schema, site-architecture and competitors.
Editing its instructions
The agent's page in the app carries the instructions it is given at the start of every run, and you rewrite them there — the pages that matter, the problems you would rather it left alone. The cadence is not editable. The switch reads on, off or paused, where paused means Kwern stopped it for a reason and will resume it when that reason clears.
Reddit agent
How the Reddit agent finds the threads your product belongs in, what it reads before it drafts a reply, and why you post every one of them yourself.
Writer agent
How the Writer agent plans a content roadmap, writes one article a run from it, and why the weekly cap is the number that matters.