Edit Logging Functionality + Utilities for Next Edit #6268

adarshramiyer · 2025-06-23T22:52:03Z

Description

Logs user editing data to construct a next-edit-prediction dataset, as follows:
Introduces capability to aggregate (chunk) user actions into coherent edits based on spatial and temporal locality. Captures the user cursor position before the edit and after the previous edit, for use in constructing an editable-region excerpt. Establishes a pipeline to get autocomplete context snippets manually, which is useful for logging alongside edits. Routes items necessary for edit logging to dev data using a new nextEdit schema, conditional on the user enabling this experimental feature. Limits logging to the open-source continue repo for data safety.

This PR also includes several of @jpoly1219's updates which lay foundations for next edit functionality. These are disabled for now.

EDIT: @jpoly1219 merged his changes here as well ( see #6287 ). They show up under this PR.

Checklist

I've read the contributing guide
The relevant docs, if any, have been updated or created
The relevant tests, if any, have been updated or created

…ture/next-edit-mvp

…laggy

…to jacob/feature/next-edit-mvp

…s context to vscode messenger

…ture/next-edit-mvp

Jacob/feature/next edit mvp

Patrick-Erichsen

Cool to run this locally and see my first next edit prediction! Worked well for the most part, some of the insertion logic felt a bit off but will start to share more concrete examples of that once we get this shipped.

I got this error trying to use the feature with a Hub secret, but didn't get the error with a hardcoded API key, so probably fine to ignore for now:

HTTP 500 Internal Server Error from https://api.continue-stage.tools/model-proxy/v1/chat/completions Error in Continue server: 502 Bad Gateway

Lot of code in the PR so I didn't dive too deep into the meat of the nextEdit code.

A few high level thoughts as we build out the feature

Where are there opportunities to unit test some of the behavior? Benefits being to provide examples of expected inputs/outputs, speed up feedback loops (eg the agent can run the tests to iterate on your feedback), lockdown behavior, etc. Unit tests are pretty easy to write with LLMs
We tend to not comment our code very heavily, but in this case with you guys building a large feature but not necessarily being around afterwards to maintain it, I would like to err on the side of over-communication/documentation in the code. I think what this looks like in practice: a nextEdit/README.md with things like general feature overview, basic diagrams, concept definitions, etc; comments on non-obvious params, functions, etc
e2e tests for a sanity check that next edit is working would be nice. This might be a bit tricky with the experimental toggle. One way we could maybe get around that is by just enabling next edit by default for Continue org members

core/config/sharedConfig.ts

Patrick-Erichsen · 2025-06-25T15:29:34Z

core/core.ts

+    on("files/smallEdit", async ({ data }) => {
+      const EDIT_AGGREGATION_OPTIONS = {
+        deltaT: 1.0,
+        deltaL: 5,
+        maxEdits: 250,
+        maxDuration: 100.0,
+        contextSize: 5,
+      };
+
+      if (!global._editAggregator) {
+        global._editAggregator = new EditAggregator(
+          EDIT_AGGREGATION_OPTIONS,
+          (
+            beforeAfterdiff: BeforeAfterDiff,
+            cursorPosBeforeEdit: Position,
+            cursorPosAfterPrevEdit: Position,
+          ) => {
+            NextEditProvider.getInstance().addDiffToContext(
+              createDiff(
+                beforeAfterdiff.beforeContent,
+                beforeAfterdiff.afterContent,
+                beforeAfterdiff.filePath,
+                DiffFormatType.Unified,
+              ),
+            );
+
+            // Get the current context data from the most recent message
+            const currentData = (global._editAggregator as any)
+              .latestContextData || {
+              configHandler: data.configHandler,
+              getDefsFromLspFunction: data.getDefsFromLspFunction,
+              recentlyEditedRanges: [],
+              recentlyVisitedRanges: [],
+            };
+
+            void processNextEditData(
+              beforeAfterdiff.filePath,
+              beforeAfterdiff.beforeContent,
+              beforeAfterdiff.afterContent,
+              cursorPosBeforeEdit,
+              cursorPosAfterPrevEdit,
+              this.ide,
+              currentData.configHandler,
+              currentData.getDefsFromLspFunction,
+              currentData.recentlyEditedRanges,
+              currentData.recentlyVisitedRanges,
+              currentData.workspaceDir,
+            );
+          },
+        );
+      }
+
+      const workspaceDir =
+        data.actions.length > 0 ? data.actions[0].workspaceDir : undefined;
+
+      // Store the latest context data on the aggregator
+      (global._editAggregator as any).latestContextData = {
+        configHandler: data.configHandler,
+        getDefsFromLspFunction: data.getDefsFromLspFunction,
+        recentlyEditedRanges: data.recentlyEditedRanges,
+        recentlyVisitedRanges: data.recentlyVisitedRanges,
+        workspaceDir: workspaceDir,
+      };
+
+      // queueMicrotask prevents blocking the UI thread during typing
+      queueMicrotask(() => {
+        void global._editAggregator.processEdits(data.actions);
+      });
+    });
+


Could we pull this out into a helper fn in the nextEdit folder? This file has a lot of inline fn definitions like this but we've been trying to avoid it.

resolved as per commit 7aebea0

Patrick-Erichsen · 2025-06-25T15:32:14Z

core/nextEdit/context/aggregateEdits.ts

+export interface EditClusterConfig {
+  deltaT: number;
+  deltaL: number;
+  maxEdits: number;
+  maxDuration: number;
+  contextSize: number;
+  contextLines: number;
+  verbose: boolean;
+}


Comments on what these are would be helpful. Most are somewhat self-explanatory but the delta ones I don't know

This probably goes for most of the interfaces. Would be nice to have this well documented.

resolved as per commit 7aebea0

Patrick-Erichsen · 2025-06-25T15:34:00Z

core/core.ts

+          (
+            beforeAfterdiff: BeforeAfterDiff,
+            cursorPosBeforeEdit: Position,
+            cursorPosAfterPrevEdit: Position,
+          ) => {
+            NextEditProvider.getInstance().addDiffToContext(
+              createDiff(
+                beforeAfterdiff.beforeContent,
+                beforeAfterdiff.afterContent,
+                beforeAfterdiff.filePath,
+                DiffFormatType.Unified,
+              ),
+            );
+
+            // Get the current context data from the most recent message
+            const currentData = (global._editAggregator as any)
+              .latestContextData || {
+              configHandler: data.configHandler,
+              getDefsFromLspFunction: data.getDefsFromLspFunction,
+              recentlyEditedRanges: [],
+              recentlyVisitedRanges: [],
+            };
+
+            void processNextEditData(
+              beforeAfterdiff.filePath,
+              beforeAfterdiff.beforeContent,
+              beforeAfterdiff.afterContent,
+              cursorPosBeforeEdit,
+              cursorPosAfterPrevEdit,
+              this.ide,
+              currentData.configHandler,
+              currentData.getDefsFromLspFunction,
+              currentData.recentlyEditedRanges,
+              currentData.recentlyVisitedRanges,
+              currentData.workspaceDir,
+            );
+          },
+        );


Could we pull this out into a function def instead of defining it anonymously in the callback?

resolved as per commit 7aebea0

Patrick-Erichsen · 2025-06-25T15:36:07Z

core/nextEdit/context/processNextEditData.ts

+export const processNextEditData = async (
+  filePath: string,
+  beforeContent: string,
+  afterContent: string,
+  cursorPosBeforeEdit: Position,
+  cursorPosAfterPrevEdit: Position,
+  ide: IDE,
+  configHandler: ConfigHandler,
+  getDefinitionsFromLsp: GetLspDefinitionsFunction,
+  recentlyEditedRanges: RecentlyEditedRange[],
+  recentlyVisitedRanges: AutocompleteCodeSnippet[],
+  workspaceDir: string,
+  modelNameOrInstance?: string | undefined,
+  // eslint-disable-next-line max-params
+) => {


I would agree with the eslint-disable-next-line max-params here 😅

The easy/nice fix is to just define a single param which is an object. The main benefits here are that 1) it makes each param more clear, and 2) you can pass the args in any order you want

Suggested change

export const processNextEditData = async (

filePath: string,

beforeContent: string,

afterContent: string,

cursorPosBeforeEdit: Position,

cursorPosAfterPrevEdit: Position,

ide: IDE,

configHandler: ConfigHandler,

getDefinitionsFromLsp: GetLspDefinitionsFunction,

recentlyEditedRanges: RecentlyEditedRange[],

recentlyVisitedRanges: AutocompleteCodeSnippet[],

workspaceDir: string,

modelNameOrInstance?: string | undefined,

// eslint-disable-next-line max-params

) => {

interface ProcessNextEditDataParams {

filePath: string;

beforeContent: string;

afterContent: string;

cursorPosBeforeEdit: Position;

cursorPosAfterPrevEdit: Position;

ide: IDE;

configHandler: ConfigHandler;

getDefinitionsFromLsp: GetLspDefinitionsFunction;

recentlyEditedRanges: RecentlyEditedRange[];

recentlyVisitedRanges: AutocompleteCodeSnippet[];

workspaceDir: string;

modelNameOrInstance?: string | undefined;

}

export const processNextEditData = async ({

filePath,

beforeContent,

afterContent,

cursorPosBeforeEdit,

cursorPosAfterPrevEdit,

ide,

configHandler,

getDefinitionsFromLsp,

recentlyEditedRanges,

recentlyVisitedRanges,

workspaceDir,

modelNameOrInstance,

}: ProcessNextEditDataParams) => {

Thanks! resolved as per commit 7aebea0

core/syntaxHighlighting/SyntaxHighlighter.ts

Patrick-Erichsen · 2025-06-25T17:42:13Z

core/nextEdit/templating/NextEditPromptEngine.ts

+  content: string;
+}
+
+export function renderDefaultSystemPrompt(): SystemPrompt {


I think this would be easier to read if it was written as a template literal instead of an array of strings. We do that for our other system messages.

Also, thoughts on adding an example in this prompt? Feels likely that would help.

Using templates now. I feel like the template makes it self-explaining, but let me know if you think otherwise.

core/nextEdit/templating/NextEditPromptEngine.ts

Co-authored-by: Patrick Erichsen <[email protected]>

jpoly1219 and others added 30 commits June 13, 2025 17:49

add tests for next edit tasks

f62bfe6

add a function to extract snippets without race

065ac51

toggle between models

bd666c5

define types

ebed592

add prompt generators

9ddb226

default to next edit for now

ba7e160

Merge branch 'main' of github.com:continuedev/continue into jacob/fea…

651f10a

…ture/next-edit-mvp

use llm.chat instead of env vars

e218852

call next edit provider

e6ab397

add recently opened file snippets

2f9e5eb

pass in default abort controller signal

aafb95a

render diff as ghost text (albeit by an entire line worth of diff)

015c8fa

add a function to create a renderable diff given DiffLines

a6982b9

add a util function to replace all escaped characters

d44c533

remove unnecessary slice

69f3a54

initialize next edit window manager on vscode extension activate

0d37e9b

return undefined for next edit

6dfe33d

create a next edit window manager singleton

00d850a

add ctrl+space esc to hide next edit window

bcc8c2d

Merge branch 'main' of github.com:continuedev/continue into jacob/fea…

a29fbe7

…ture/next-edit-mvp

Merge branch 'main' of github.com:continuedev/continue into jacob/fea…

242b278

…ture/next-edit-mvp

fix margins

985233a

basic action chunking in place for edit diff logging

7ec4bc2

render leading whitespaces

8030843

improved edit logging behavior, working on optimizing performance now

3202b2d

completed some performance optimizations that make edit logging less …

2630d89

…laggy

cleanup in prep for devData logging

3d851d1

created diff formatting utils for later

b0a5c78

update colors to use css variables

811ee3e

revert back to hardcoded values

4502bc5

jpoly1219 added 23 commits June 24, 2025 13:16

stop rendering empty artifacts

52d857d

Merge branch 'feature/nextEdit' of github.com:continuedev/continue in…

46fd9eb

…to jacob/feature/next-edit-mvp

resolve next edit merge diffs

e64d4b4

add type definitions and interfaces for opt in continue features

66a1dc9

setup and clear next edit window manager on optInContinueFeature, pas…

1ef84a0

…s context to vscode messenger

add a static method to delete the current instance

b0043c9

check if next edit is instantiated

0567e0c

create a component to house all toggles internal to the team

a9dbc47

render internal toggles menu for continue team members

09a395e

extend tab and esc to accept or reject when nextEditWindowActive is true

fbcf27a

toggle between autocomplete and next edit

746b0b6

toggle between autocomplete and next edit

8e4e9dc

Merge branch 'main' of github.com:continuedev/continue into jacob/fea…

8ae5b4e

…ture/next-edit-mvp

rename to optInNextEditFeature

11a28c8

dynamically render theme, font size, and font family

c491eab

remove unnecessary imports

eb3dae6

reset nextEditWindowActive contexts to false for failsafe

b763713

create a helper function to get the color theme string only

9db09a7

do an initial load on start

6502624

add next edit test cases

cee66e5

rename option

4207228

add unified diff to context

1928250

Merge pull request #6287 from continuedev/jacob/feature/next-edit-mvp

4bcf69f

Jacob/feature/next edit mvp

Patrick-Erichsen requested changes Jun 25, 2025

View reviewed changes

github-project-automation bot moved this from Todo to In Progress in Issues and PRs Jun 25, 2025

adarshramiyer and others added 4 commits June 26, 2025 13:42

Update core/config/sharedConfig.ts

24a9efe

Co-authored-by: Patrick Erichsen <[email protected]>

refactoring and commenting to address patrick's comments

7aebea0

proper singleton pattern for editAggregator; no longer a global var

2f196cb

remove unidiff console log

f8d7f9f

jpoly1219 mentioned this pull request Jun 28, 2025

Updates on Next Edit PR #6334

Open

3 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Edit Logging Functionality + Utilities for Next Edit #6268

Edit Logging Functionality + Utilities for Next Edit #6268

adarshramiyer commented Jun 23, 2025 •

edited

Loading

Uh oh!

Patrick-Erichsen left a comment

Uh oh!

Uh oh!

Patrick-Erichsen Jun 25, 2025

Uh oh!

adarshramiyer Jun 26, 2025

Uh oh!

Patrick-Erichsen Jun 25, 2025

Uh oh!

Patrick-Erichsen Jun 25, 2025

Uh oh!

adarshramiyer Jun 26, 2025

Uh oh!

Patrick-Erichsen Jun 25, 2025

Uh oh!

adarshramiyer Jun 26, 2025

Uh oh!

Patrick-Erichsen Jun 25, 2025

Uh oh!

adarshramiyer Jun 26, 2025

Uh oh!

Uh oh!

Uh oh!

Patrick-Erichsen Jun 25, 2025

Uh oh!

jpoly1219 Jun 27, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Edit Logging Functionality + Utilities for Next Edit #6268

Are you sure you want to change the base?

Edit Logging Functionality + Utilities for Next Edit #6268

Conversation

adarshramiyer commented Jun 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Checklist

Uh oh!

Patrick-Erichsen left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

adarshramiyer commented Jun 23, 2025 •

edited

Loading