Repository navigation
(janitor/dead-code): remove orphaned cloud-agent-next components and hook - #7974
Merged
kilo-code-bot[bot] merged 1 commit intoOct 19, 2026
Merged
Conversation
Delete five cloud-agent-next files that are unreachable from any entry point and have no remaining consumer: - ErrorBanner.tsx (superseded by inline indicators) - OrgContextModal.tsx - ResumeConfigModal.tsx - TodoReadToolCard.tsx - hooks/useOrgContextCommand.ts Repository-wide searches find no import, re-export, dynamic import, barrel export, story, or configuration reference to any of them; only stale prose comments remain. The typecheck and oxlint passes confirm no module referenced the deleted files.
Contributor
Author
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryVerified that the five deleted Files Reviewed (5 files)
Verification Notes
This is a deletion-only diff with no added lines, so there are no commentable changed lines and no findings to report. Reviewed by deepseek-v4.1-flash · Input: 38.2K · Output: 4.1K · Cached: 253.4K Review guidance: REVIEW.md from base branch |
Contributor
Author
|
Meta Janitor: Safety review passed; requesting approval. |
Contributor
There was a problem hiding this comment.
Meta-janitor safety approval for 3875b07. Signal: #7974 (comment). GitHub auto-merge remains responsible for merging.
kilo-code-bot
Bot
deleted the
janitor/dead-code-cloud-agent-next-orphans
branch
October 19, 2026 11:10
This was referenced Oct 19, 2026
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.
What was deleted
Five files under
apps/web/src/components/cloud-agent-next/, all unreachable from any entry point:ErrorBanner.tsx— error banner superseded by inline indicators (event-processor.tscomments document the deliberate removal)OrgContextModal.tsx— organization-context chooser that is never renderedResumeConfigModal.tsx— CLI-session resume config modal that is never renderedTodoReadToolCard.tsx— todo "read" tool card that is never dispatchedhooks/useOrgContextCommand.ts— org-context command hook with no caller606 lines removed, no production behavior change.
Evidence of unreachability
ErrorBanner,OrgContextModal,ResumeConfigModal,TodoReadToolCard,useOrgContextCommand) across*.ts,*.tsx,*.js,*.json,*.md,*.mjs,*.css,*.yamlfinds no import, re-export, dynamic import, or string reference — only stale prose comments (// No ErrorBanner …,* Used by ResumeConfigModal …).cloud-agent-nexthas noindex.ts, and noexport * from './ErrorBanner'(or equivalent) exists anywhere.MODESandVALID_MODE_VALUES(the only extra exports fromResumeConfigModal) are not imported anywhere;ResumeConfigis defined and used via./types, so the redundant re-export removed here had no consumer.kilocodeexternal consumer repo was cloned and searched: no reference (only unrelatedStartupErrorBannersubstring matches).Dynamic and configured entry points checked
src/components/, notsrc/app//src/pages/, so nopage/route/layoutdiscovery applies.next/dynamicorimport(...)loads them.package.jsonexports (they are internal toapps/web, not a published package).dev/, or examples.Contract and compatibility considerations
updateOrgContextAtominstore/db-session-atoms.tsbecomes an unused internal export (its only caller wasuseOrgContextCommand) but is left in place because it writes theorgContext/orgContextConfirmedfields that are part of the persistedIndexedDbSessionDatashape.Validation
tsgo --noEmit -p apps/web/tsconfig.json(web typecheck): pass, before and after deletion.oxlint --config .oxlintrc.json apps/web/src/components/cloud-agent-next: 0 warnings, 0 errors.git diff --check: clean.next buildwas not run because this environment has no PostgreSQL/Redis.