#6517 [Other] Feature request: rename-aware editing, an integrated debugger, and an optional reviewer model
open · @xvcezrqpbxtpzblrt · 2 Kommentare · Auf GitHub
Setup & installNVIDIA / CUDAModels & quantsWindows
Beschreibung
## Environment - GPU: NVIDIA GeForce RTX 3080 Ti Laptop GPU, 16384 MiB (16 GB) VRAM - RAM: 63.71 GB - OS: Microsoft Windows 11 Pro, build 26300 - Strata: 0.2.18 ## Request Please confirm scope first: this covers three separate, substantial capabilities. Each should be opt-in, off by default, and leave existing behavior unchanged unless the option is enabled. ## 1. Rename-aware, reference-aware code editing User need: when I ask the assistant to rename a symbol or move a file, I expect every reference, re-export and import across the project to be updated, the way an editor would. Today I have to ask it to search and edit files one by one, and aliases and indirection files get missed. Current state (unconfirmed static analysis of the 0.2.18 source): the host maps a read-only tool named `lsp`, described only as "Looks up how the code fits together", and places it in the set of tools that cannot change anything on the machine. No prepare-rename, references or workspace-edit protocol call appears in this repository. The tool set itself comes from an external component whose implementation is not in this repository, so its actual capability cannot be verified here. Proposed: a rename/move operation that resolves references through a language server and applies the edits as a reviewable change, with a clear list of files touched. ## 2. Integrated debugger User need: when a program the assistant helped build crashes or hangs, I want it to inspect the failure with a real debugger - set a breakpoint, step, read the stack and variables - instead of guessing from print statements. Current state (unconfirmed static analysis): there is no debug-adapter protocol, breakpoint management, or attach-to-crash implementation in this repository, and the product explicitly suppresses debugger backtraces on a user's machine. The current workaround is to run a debugger in a terminal myself and paste the output into the chat. Proposed: an opt-in debug tool that starts a debug session against a local process, exposes breakpoints, stepping, stack and variables, and lets the assistant read the result. ## 3. An optional reviewer model User need: I want to assign a second model to read the main assistant's turns and inject short notes when it spots a problem, on its own context and model, without stopping the main run. Today my workaround is to open a separate chat and ask a model to review what the first one did, which is manual and happens after the fact. Current state (unconfirmed static analysis): there is no setting, API parameter or UI control for a reviewer role. The existing "interject" setting is about the person pressing Enter while the assistant is still answering; the approval gate asks the person, not a model; the bundled review prompt runs only when invoked manually. The `time_skip` flow records "advice" checks but explicitly excludes them from decisions, which is a different mechanism. Proposed: an opt-in reviewer role with its own model and context that observes turns and posts inline notes; the main assistant can act on a note or explain why it is not acting on it. ## Scope and compatibility - These are new capabilities. All three stay off unless explicitly enabled, and the default path must behave exactly as before. - They touch different layers, so please confirm which of the three, if any, are in scope before implementation. ## Verification status Unconfirmed static analysis of the source at Strata 0.2.18. Not reproduced on an installed build. No logs and no screenshots. The statements above describe what this repository does and does not contain; the capability of the external component is explicitly marked as unverifiable here. ## What would verify each item - Rename a symbol used in several files, then check that references and imports are all updated and listed. - Run a crashing program, then check that a debug session can attach, step, and read the stack. - Enable a reviewer model, then check that notes appear during a turn without stopping it, and that turning it off changes nothing.
Mehr auf der Site
Links zu Install, Modellen, Releases.