Skip to content

feat(site): describe @falai/agent 4 on the home page and read docs from 4.x - #3

Merged
gusnips merged 3 commits into
mainfrom
v4-docs
Oct 2, 2026
Merged

gusnips merged 3 commits into
mainfrom
v4-docs

Conversation

@gusnips

@gusnips gusnips commented Oct 2, 2026 •

Copy link
Copy Markdown
Collaborator

Moves the site to 4.0.0.

  • package.json: @falai/agent ^3.4.4 to ^4.0.0. Docs, examples, version badge and sidebar are generated from the package, so the whole docs tree becomes the v4 docs, including the v3-to-v4 migration page.
  • Home page: install line, one-call example (agent.turn with a message), and the full agent in English. Snippet typechecked against the 4.0.0 tarball. Cards now cover flows and steps, fields, the two-call budget, Store, FlowSpec. New "Coming from 3.x?" button links to /docs/migration/v3-to-v4.
  • README: fixed the metadata command name; meta description updated.

Blocked until 4.0.0 is on npm (latest is 3.4.5, alpha 4.0.0-alpha.28 today). After publish, run bun install to refresh bun.lock, because CI uses --frozen-lockfile. Build, tsc and eslint pass locally against the packed 4.0.0 tarball.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

…om 4.x

The home page still showed the 3.x API (agent.route, agent.send, Agent<TContext, TData>) and the package range was ^3.4.4, so the docs, version badge and sidebar came from 3.x. The dependency is now ^4.0.0 and the quick start is the 4.0.0 quickstart example in English (typechecked against the packed 4.0.0 tarball): fields, a flow with steps, agent.turn(). Feature cards describe flows, fields, the two-call budget, Store and FlowSpec. The hero links to the v3 to v4 migration guide. README and meta description fixed too.
4.0.0 is on npm, so the lockfile can resolve the ^4.0.0 range that CI's frozen install needs.
@gusnips
gusnips marked this pull request as ready for review October 2, 2026 03:04
A pull request run deployed with channelId live, so a PR branch could
publish itself to the production site, and then failed on the comment
step because the token cannot write to pull requests. Pull requests now
build only; main still deploys.
@gusnips
gusnips merged commit e81f575 into main Oct 2, 2026
1 check passed
@gusnips
gusnips deleted the v4-docs branch October 2, 2026 03:11
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