Bohdan Triapitsyn
34d0ff7383
A diff is ordered by file path, which is almost never the order in which a change makes sense. This adds a Walkthrough surface that reorders it: the model groups related hunks into stops, explains what each group changes about behavior, and orders the stops so each builds on the last. It explains and orders; judging code stays with the existing Review action. Reviews uncommitted work (all, staged, unstaged), a branch against its base, or a pull request. Generation is always user-initiated — nothing runs on a timer, on a file change, or as a side effect of opening a panel. Invariants worth preserving: - Hunk identity is derived on the server and only there. Ids are content hashes, so an anchor that no longer resolves is proof the code it described changed, and staleness needs no heuristics. The client matches ids to ids and never recomputes them; two implementations would have to agree forever. - The digest is never truncated. A diff that does not fit the model's context is refused with an actionable reason, because a walkthrough written against half a diff reads as confident and is wrong. - Nothing disappears. Lockfiles and other generated output are excluded from the model's input by name — never by size — and everything no stop covers is listed at the end, so "have I seen all of it" stays answerable. - Cost is explicit. Results are content-addressed, so returning the working tree to an earlier state costs nothing; generation outlives its request, so a refresh detaches the client rather than discarding paid-for work, and only an explicit cancel stops it. Supporting changes to shared modules: - git: expose the existing getRangeDiff as GET /api/git listUntrackedPaths and getUntrackedDiffs. The latter resolve the repository once for a batch instead of per file, taking a panel ~340ms on an 80-file working tree. - small-model: structured output across four wire forma and abort signal, and an onOverflow policy so an oversized prompt fails loudly instead of being silently clipped. A provider remembered so the prompt-side fallback goes first next time. - models.dev metadata: surface structured_output as tri false blocks a model, a missing field does not, because the catalog omits it for roughly half of all models. Desktop and tablet only: VS Code serves Git through its these routes, and the mobile shell does not consume the surface registry. Docs: packages/docs walkthrough page in English and all eight locales.
39 lines
1.4 KiB
JavaScript
39 lines
1.4 KiB
JavaScript
import fs from 'fs';
|
|
import os from 'os';
|
|
import path from 'path';
|
|
|
|
// The walkthrough may run on a different model than the rest of the small-model
|
|
// callers. Those callers want cheap and fast; this one needs structured output
|
|
// and enough context for a whole diff, and forcing one setting to serve both
|
|
// means the user has to degrade one feature to fix the other.
|
|
|
|
const SETTINGS_FILE = path.join(
|
|
process.env.OPENCHAMBER_DATA_DIR
|
|
? path.resolve(process.env.OPENCHAMBER_DATA_DIR)
|
|
: path.join(os.homedir(), '.config', 'openchamber'),
|
|
'settings.json',
|
|
);
|
|
|
|
/**
|
|
* The explicit walkthrough model, or `null` to fall back to normal small-model
|
|
* resolution.
|
|
*
|
|
* Having chosen a model *is* the opt-out; a separate toggle would let the two
|
|
* disagree, and then clearing the picker would leave a setting that says "do
|
|
* not use the small model" with nothing to use instead.
|
|
*/
|
|
export function readWalkthroughModelOverride() {
|
|
try {
|
|
const settings = JSON.parse(fs.readFileSync(SETTINGS_FILE, 'utf8'));
|
|
if (!settings || typeof settings !== 'object') return null;
|
|
const override = typeof settings.walkthroughModelOverride === 'string'
|
|
? settings.walkthroughModelOverride.trim()
|
|
: '';
|
|
return override || null;
|
|
} catch {
|
|
// No settings file, unreadable, or malformed all mean the same thing: no
|
|
// override, use the small model.
|
|
return null;
|
|
}
|
|
}
|