Skip to content

docs(seo): bring llms.txt and llms-full.txt up to 0.5.6 - #747

Merged
chaitanyagiri merged 3 commits into
mainfrom
seo-engine/llms-txt-refresh
Oct 16, 2026
Merged

chaitanyagiri merged 3 commits into
mainfrom
seo-engine/llms-txt-refresh

Conversation

@chaitanyagiri

@chaitanyagiri chaitanyagiri commented Oct 15, 2026 •

Copy link
Copy Markdown
Collaborator

What changed

  • docs/llms.txt: the hand written top was from August. It said "Current version: 0.4.6", linked the old repository path, and said code "never leaves your machine". It now gives the house description, "Current version: 0.4.6" for the source in this repository (the release link check compares that line with package.json, and the 0.5.5 release carries installers only), the latest app release 0.5.5 (1 Oct 2026), the engines the README lists, the download page, the HarnessMD repository, the Agent Gallery, the telemetry note, Free and Pro in one line, 15 current guides and 8 comparisons. The generated blog list between the BLOG markers is untouched (the build rewrote it byte for byte).
  • docs/llms-full.txt: last changed 13 Aug. It said "Current version: 0.3.8" and "Free forever; no paid tier". Rewritten from the current README: what the app does, Free and Pro, install in three steps plus build from source, where it runs and what telemetry sends, and the guides by topic. Every guide link points at a post that exists.

No price, no star count, no download count, and no claim about 0.5.6. robots.txt and sitemap.xml are already current (the sitemap is rebuilt with every blog build).

Checks

  • npm run build in blog: passes; the only changed files are these two.
  • node tools/check-release-links.cjs: "release links consistent at v0.4.6" (the first push failed it because the version line was gone; fixed in the second commit).
  • Every blog link in both files checked against blog/src/posts/.

Not in this PR: harnessmd.com has no llms.txt or robots.txt (both 404). That site is not in this repository.

Before

Live today.

before llms.txt
before llms-full.txt

After

This branch.

after llms.txt
after llms-full.txt

17 Oct update: 0.5.6

Latest app release is now 0.5.6 (17 October 2026). Both files name Capabilities, Integrations and Teams, give Pro at $150 a year and free for everyone who signs in until Saturday 24 October 2026, and point release notes at harnessmd.com/download#whats-new, since GitHub has no 0.5.6 release. "Current version: 0.4.6" stays, pinned to package.json by the release link check.

🤖 Generated with Claude Code

The hand written top of llms.txt still said 0.4.6 and pointed at the old
repository path; llms-full.txt said 0.3.8 and "no paid tier". Both now
describe the app as it ships today, link the download page and the
HarnessMD repository, list the current guides and comparisons, and name
Pro as an optional plan. The generated blog list is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tools/check-release-links.cjs reads "Current version: x.y.z" from
docs/llms.txt and compares it with package.json (0.4.6). The 0.5.5
release carries installers only, not the 0.5.5 source, so both files now
give the source version and the latest app release separately.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Latest app release is 0.5.6 (17 October 2026). Both files name Capabilities,
Integrations and Teams, give Pro at $150 a year and free for everyone who
signs in until Saturday 24 October 2026, and point release notes at the
download page, since GitHub has no 0.5.6 release. "Current version: 0.4.6"
stays: the release link check pins it to package.json.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chaitanyagiri chaitanyagiri changed the title docs(seo): llms.txt and llms-full.txt up to 0.5.5 docs(seo): bring llms.txt and llms-full.txt up to 0.5.6 Oct 16, 2026
@chaitanyagiri
chaitanyagiri merged commit a6241f5 into main Oct 16, 2026
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant