Conversation
Gate operator-facing wiki chrome behind WIKI_UI_ENABLED (default false): nav, sidebar CTAs, and /wiki routes redirect to /knowledge. Move wiki model/API-key settings out of Settings → Advanced onto /wiki/settings so re-enabling the flag restores them with the wiki tab, not Advanced. Co-authored-by: Jaime Ginorio <jaime.ginorio@finditpr.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Layout-only Next redirect used a meta refresh (HTTP 200). Add next.config redirects gated by the same WIKI_UI_ENABLED flag so /wiki, /wiki/ask, and /wiki/settings return 307 to /knowledge. Co-authored-by: Jaime Ginorio <jaime.ginorio@finditpr.com>
Owner
Author
|
Superseded by #78, which removes Wiki and Conflicts from the shipping surface (nav, routes, retrieve/ingest/MCP evidence) instead of hiding wiki behind Useful bits from this PR (Settings → Advanced embeddings-only, wiki settings at Please close this PR without merging. |
jginorio
changed the title
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
2 participants
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.
Why
Wiki auto-gen is paused / undecided. Operator chrome still treated wiki as a live product surface (nav, Ask/Go to wiki, Settings → Advanced wiki model). That confused people. Retrieval stays raw-first; MCP
search_knowledgealready excludeswiki/.Jaime: hide wiki from the UI; wiki settings belong under the wiki tab, not Advanced.
What changed
Hide all operator-facing wiki UI behind
WIKI_UI_ENABLEDinweb/lib/wiki-ui.ts(defaultfalse). Server/API,wiki-generator-ts/, and CDK wiki image are unchanged. Schedules /AUTO_TRIGGER_CODE_WIKIare not touched.Entry points gated or removed
/wiki)/wiki/ask) and Go to wiki/wiki,/wiki/ask,/wiki/settings→ HTTP 307 to/knowledge(next.config.ts+ layout backstop)Wiki settings home (for when we turn the flag back on)
Wiki model / BYO API-key controls moved from Settings → Advanced to
/wiki/settings, colocated withweb/app/wiki/. The wiki page toolbar has a Settings button. Settings → Advanced is embeddings-only.How to re-enable later
Set
WIKI_UI_ENABLEDtotrueinweb/lib/wiki-ui.ts. That restores Wiki nav,/wiki(no redirect), Ask the brain, and/wiki/settings. Do not hunt call sites. Do not flip EventBridge wiki schedule orAUTO_TRIGGER_CODE_WIKIas part of a UI re-enable.Tests
web/npm test— 117 passed (includeswiki-uitests: flag off, nav omits Wiki, settings href is/wiki/settings)next build— compiled successfully; TypeScript finished clean/wiki,/wiki/ask,/wiki/settings→307/knowledge