feat: use generated AI docs in local circuit prompt#84
Conversation
|
CI note: the type-check workflow is green. The Bun Test workflow is failing because the fork/PR run has no |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a85688371f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| The following context is fetched from ${TSCIRCUIT_AI_DOCS_URL}. It is auto-generated and kept up to date by the tscircuit docs site. Prefer this documentation over stale hand-written component notes when deciding which props, components, and patterns are supported. | ||
|
|
||
| ${cleanedPropsDoc} | ||
| ${cleanedTscircuitAiDocs} |
There was a problem hiding this comment.
Bound AI docs payload before injecting into system prompt
This change replaces a narrowly scoped component-props doc with ai.txt, then injects the entire fetched payload into the system prompt without any size cap or section filtering. ai.txt is a repomix-style aggregate of many docs files, so prompt size can grow to the point that benchmark runs either fail with context-length errors or lose most of the response budget to background context instead of the user task. Please truncate and/or select only the component/props sections before interpolation.
Useful? React with 👍 / 👎.
Summary
https://docs.tscircuit.com/ai.txtValidation
./node_modules/.bin/tsc --noEmithttps://docs.tscircuit.com/ai.txtreturns HTTP 200 and the Repomix-generated docs payloadCloses #45