Skip to content
| Marketplace
Sign in
Visual Studio Code>Visualization>DiftaleNew to Visual Studio Code? Get it now.
Diftale

Diftale

Preview

Nicohash

|
4 installs
| (0) | Free
One Copilot conversation. Review AI changes with a live code graph, functional batches, diffs and security checks.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Diftale · 0.12.0

One Copilot conversation, with a clear view of every proposed change. Diftale keeps the dependency graph, functional batches, diffs and observed security results beside your chat in VS Code.

Built by Nicolas Hedoire. Diftale is a Preview release. The interface is currently in French; this English documentation uses the actual French control labels. See the Marketplace listing, publication records and validation scope for release information and evidence.

Get started

  1. Open a trusted local project in desktop VS Code 1.109 or later, with Copilot Chat installed and signed in.
  2. Open Diftale in the Activity Bar. The workflow stays on the left, your real code editor stays in the center, and Copilot stays on the right.
  3. Select Ouvrir Copilot avec Diftale. This selects the bundled Diftale agent without sending a verification message. Choose your model in Copilot and describe your change there.
  4. Copilot proposes functional batches through the native Diftale tools. Follow the single primary action on the current batch.

Copilot requires no separate Node.js installation, CLI login or MCP server for Diftale. There is no second conversation input. Tool registration means availability; a successful tool invocation establishes actual use. A reply alone does not create a batch.

Follow code in the central editor

Supported workspace edits, including unsaved buffers, automatically open a central Diff / Avant / Après view without taking focus from Copilot. Accepted batch proposals also open this view. Automatic display does not approve a batch: select Relire in the sidebar before applying it. This observes workspace changes, not private model reasoning or tokens before an edit reaches VS Code.

Use Suivi en direct to pause, or scroll in the live diff; resume with Reprendre le suivi. Observation continues while following is paused. Set codeAtlas.liveCodeView to editor to follow actual native source editors instead.

The branch header opens a local branch picker. Git refuses conflicting edits; Diftale does not stash or discard them. Unsaved source buffers must be saved before checkout.

The sidebar also shows the development server state. Start uses an existing npm dev, start or serve script, configurable with codeAtlas.devServerScript. Restart and stop control only processes started by Diftale. Configure codeAtlas.devServerUrl to monitor a loopback HTTP address when it is not printed by the process. An external server is observable but must be stopped from its own terminal. HTTP readiness is not a functional or security test. A branch change marks an owned process as requiring restart.

Changes outside a proposed plan remain visible and reviewable. Diftale does not invent batches for them. Options holds the dependency map, page preview, security results, Jira attachment, scoped local ZAP scan and diagnostics. Opening Carte selects the latest change and shows modified files as a graph, with clickable +/− file cards. Choose Tous to expand to the whole project. Deleted files remain reviewable from the cards. The graph describes indexed imports, not runtime execution. Preview requires a running application and a supported element mapping.

Branch-aware context

The sidebar and status bar show the actual Git branch, or the short commit for detached HEAD. Diftale detects branch/HEAD changes even when no source file changes, with a two-second fallback check, and refreshes Git before tool requests and guided operations.

Each branch has a separate local baseline, functional plan, batch history, goal and preview associations. Switching branches cancels the old workflow, closes its review, clears pending commit requests and detaches the selected Jira ticket. Returning restores that branch's saved plan; restored checks must be rerun. Existing changes carried through checkout remain visible outside a proposed lot. Automatic context detection never performs checkout, stash, reset, file save or commit. Checkout happens only after selecting a branch in the picker.

Context revisions include the branch identity and HEAD as well as indexed file contents. Old proposals cannot be accepted merely because two branches have identical code. A commit or reset on the same branch invalidates review and evidence. Detached commits use separate sessions. A branch rename starts a new session; deleted/recreated branches with the same name retain their saved session but Git/HEAD guards still apply. Copilot keeps its conversation: the bundled agent refreshes tool context and treats other-branch conversation history as historical. Diftale does not rewrite Copilot's private history.

Legacy unscoped plans are migrated only when their saved branch and HEAD match the current branch exactly; otherwise their local file remains intact. Tracking still uses the first workspace folder. Linked Git worktrees remain outside the guarded batch-commit workflow's supported scope.

One batch, one commit

  1. Préparer le lot sends a scoped request in the same Copilot chat. The agent reads complete files and proposes exact changes; it cannot apply them through Diftale's native tools.
  2. Relire les changements opens every proposed file in one central review tab, with Avant / Après / Diff. Opening review does not apply code. A changed proposal or source revision requires another review.
  3. Appliquer et vérifier applies the reviewed proposal, runs the project's supported npm check and the real local security checks. The guided action prefers npm test, then check, typecheck, lint or build; custom scripts may require selection. Failed or stale evidence blocks committing.
  4. After successful current checks, Diftale requests an English commit title and description in Copilot automatically. You can edit them or request a French translation. A failed suggestion still allows manual drafting.
  5. Créer le commit presents the final message and exact files in a native confirmation. It creates a local commit for this batch only; it does not push.

Explicit workflow buttons send the relevant preparation, explanation or commit-message request to Copilot. Starting the chat does not send a request. Copilot may ask for tool permissions according to your settings. Code application and committing remain explicit human actions.

Only one applied, uncommitted batch is allowed. Checks are tied to project contents and become stale after relevant edits. Security checks and test results report their actual scope; static checks are not a pentest. Optional ZAP testing requires a scoped local target and explicit confirmation. Functional explanations and acceptance criteria describe intended behavior, not proof of success.

Application is sequential and can fail after some files have changed. Undo restores only files still matching Diftale's result and preserves later human edits. Requesting correction of an applied failed batch first uses this guarded undo before asking Copilot for a revised proposal. Undo is limited to the current session. Recovery after restart or a manual commit may require Archiver le suivi, which preserves files and Git history. See plans and security.

If the panel does not follow, check Workspace Trust and Options → Diagnostic. The local report records versions, scan counts, panel readiness and actual tool activity; it excludes source, paths, conversation and ticket content and is not sent automatically.

Disable legacy nicolas-hedoire.nicohash-code-atlas or local-lab variants before enabling the public extension. Retained command and setting identifiers can conflict, and separate extension identities have separate storage.

Native tools in Copilot

Tool Purpose
diftale_get_context Read paginated project paths, a bounded graph summary, revision, workflow and attached context
diftale_get_plan Read batches, pending requests and observed check results
diftale_read_files Read up to eight complete, allowed source files
diftale_propose_plan Propose a structured plan with functional explanations
diftale_propose_batch Propose exact before/after contents for the current batch
diftale_propose_commit_message Answer the current English suggestion or translation request
diftale_explain_batch Propose the current batch's functional explanation

The bundled Diftale agent selects these tools. They cannot approve or apply edits, run a shell, launch pentests or create commits. Those controls stay in the panel. Prompts guide the model; host validation enforces supported paths, revisions and workflow scope. Copilot's general-purpose tools, other agents and manual edits remain outside these controls if you choose to use them separately.

For another compatible client, Diftale : Connecter un agent MCP still offers manual stdio configuration. That optional bridge requires Node.js 20 or later and the current VS Code window to remain open. Copilot does not register or start this bridge by default. See external-agent capabilities.

Attach a Jira ticket

Use Jira in the Diftale panel to configure Atlassian MCP and attach an issue key or link. A compact card shows the selected issue. Copilot receives the bounded ticket context through Diftale's context tool; no separate Jira tool is added to the Diftale agent.

A plan retains its own ticket snapshot. Changing or removing the selected card does not rewrite an existing plan. Diftale reads accessible sites and issues; it does not comment on issues or change their status. VS Code manages MCP authentication.

Support is limited to Jira Cloud on *.atlassian.net through Atlassian Rovo MCP. Custom domains, Data Center and other Jira MCP servers are outside this version's scope. Production Jira has not been validated end to end. The panel attachment is the supported path; merely mentioning a ticket in Copilot does not attach it. See the bundled Jira setup guide for server details.

See the rendered element while reading JSX/TSX

For a Vite JSX/TSX project, open Aperçu, attach a local page such as http://127.0.0.1:5173/, and choose Connecter le survol. Diftale adds a development connector to a supported Vite configuration and keeps a backup in .code-atlas/. Restart your Vite server yourself.

Hover over JSX/TSX in the code panel or VS Code editor to outline matching rendered DOM elements in red. This is your running application. The element must be mounted in the open page, and its source fingerprint must match the served code. Unsaved or stale code is identified; unapplied proposals are not presented as live output.

Preview controls stay dark while the page retains its own colors. The connector supports simple ESM Vite configurations and adds no production instrumentation. It does not discover routes, start a server, instrument Vue/Svelte or highlight absent elements. App security policies can prevent embedding. See visual preview.

Data and scope

Copilot can send your messages and Diftale tool results to its selected model. Results can contain paths, code, proposals, ticket context and check information. Diftale does not create another model session or import Copilot's conversation. Legacy Diftale history and provider settings may remain in local storage after upgrading, but are inactive in this workflow. See privacy and prompt policy.

Diftale follows the first workspace folder, with 300 files by default, configurable from 10 to 1,000, and 128 KiB per file. JavaScript/TypeScript imports are analyzed; JSON, CSS, SCSS, HTML, Python, Go, Rust and Markdown can also be tracked. Exclusions make analysis partial; files outside the configured limit are not tracked. Unsupported file types, oversized files and excluded folders are outside this view. TypeScript aliases, external packages and computed imports are not resolved. The guide is limited to 12 files and 24 steps.

Edit batches contain at most eight files. Hidden paths, filename-based secret exclusions, lockfiles, dependencies and generated folders are excluded from indexing, agent reads and editing; those exclusions are not comprehensive secret detection. Deletions and renames are unsupported. The integrated check-and-commit workflow requires supported npm checks and a Git repository with an initial commit; it is not universal across languages or package managers.

Existing optional Claude Code metadata hooks may still provide local events. They do not import conversations or reasoning and are not required for Copilot. The example project demonstrates the panel; it is not evidence that a real model or application test succeeded. Current verification evidence and limitations are recorded in validation.

Build and package

Building the extension, using the external MCP bridge, and running npm project checks require Node.js 20 or later. The native Copilot tools themselves use VS Code's runtime.

npm ci
npm run check
npm test
npm run package

The local package uses local-lab.diftale and produces ../diftale-0.11.0.vsix. The public package uses nicolas-hedoire.diftale and produces ../nicolas-hedoire.diftale-0.11.0.vsix, with the display name Diftale. package:marketplace requires an explicit publisher and only builds a package; publication is separate. See publication and branding.

MIT license; see the bundled LICENSE.txt. Some analysis principles are inspired by REA, as described in REA inspiration. No REA engine is bundled.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft