Repository navigation
feat: info().agent carries the program's name, a description and conversation starters - #986
Merged
Merged
Conversation
…ersation starters An instance's name was the only name info() reported, and a client had no author-written starters to offer. info() now has an agent group beside the instance's name.
…a blank package description is none
This was referenced Nov 9, 2026
Merged
kid7st
added a commit
that referenced
this pull request
Nov 9, 2026
## Release v0.30.3 Bump `@fastagent-sh/fastagent` from 0.30.2 to 0.30.3. ## Changed - **`info()` reports how the agent presents itself** (#986, part of #894). A new `info().agent` holds `name` (the program's: `package.json`'s `name`, else the directory's), `description` and `starters` (example first messages a client may offer as editable drafts; choosing one sends nothing). `info().name` stays the instance's name. `fastagent info` prints them, and `--json` adds `agent`. - `starters` is `defaults.starters` in `fastagent.config.ts`; an instance's `fastagent.json` may set its own `starters` and `description`. At most 6 starters of at most 200 characters, none blank, checked by the instance configuration's JSON Schema. - The description is the instance's `description`, else `package.json`'s; the definition now carries it and `fastagent build` writes it into the generated entry. ## Breaking changes No compatibility layer, as before 1.0. - `info().description` is now `info().agent.description`, and `AgentInfo` has a required `agent`. A client of this version against an older server fails to decode `info`. - `AgentConfig.name` is removed from `fastagent.config.ts` (it changed `definition.name` but not `dist/package.json`'s name). Name the program in `package.json`. - `description` is no longer a `fastagent.config.ts` key. Both fail as `unknown key`. ## Verification `npm run lint`, `npm run typecheck`, `npm pack --dry-run --json`. The code is the merge commit of #986, whose full gate (`npm test`: 195 files, 2388 passed, 3 skipped) and CI passed.
25 of 31 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #894: author-written conversation starters and the program's name for clients. The avatar from that issue is not included.
Behavior
info()gains anagentgroup;namestays the instance's name.agent.nameis the program's name:package.json'sname, else the directory's. It is always present.agent.descriptionis the instance'sdescription, elsepackage.json'sdescription.agent.startersare example first messages. A client may put one in a composer as an editable draft; reading or choosing one never sends anything.Where each value is written:
package.jsonfastagent.config.tsfastagent.jsondefaults.startersstartersanddescriptionare validated by the instance configuration's JSON Schema (at most 6 starters of at most 200 characters, none blank), so the program's defaults andfastagent.jsonshare one check, andfastagent buildpublishes it for editors. Sources are recorded like any other value.fastagent infoprints the program's name (when it differs from the instance's), the description and the starters, and--jsonaddsagentwith the same three values.The definition now carries
descriptionfrompackage.json, andfastagent buildwrites it into the generated entry besidenameandversion.Breaking changes
No compatibility layer, per the maintenance policy.
info().descriptionis nowinfo().agent.description(SPEC.md §3).AgentConfig.nameis removed: it changeddefinition.namebut notdist/package.json's name, so the two could disagree. Set the name inpackage.json.descriptionis no longer afastagent.config.tskey; both now fail asunknown key.Verification
npm run lint,npm run typecheck,npm test(195 files, 2387 tests). New tests: in-process and HTTP conformance ofinfo().agent, thepackage.jsontoinfo()wiring with an instance override, the resolved config's sources, and refusals of invalid description and starters.Known limitations
dist/that setsnamein its config still opens, since a built config is not re-checked.