Forge Download

A DevFoundry product

Release

Forge 0.2.1 — Preview

In-place install over Forge 0.2.0. Forge Projects and durable local conversations from 0.2.0 are included; the previous release on this site was 0.1.3. Distributed through the Visual Studio Marketplace, the Open VSX Registry, and as a VSIX from this site.

Download Forge 0.2.1 Visual Studio Marketplace Open VSX / Cursor Installation & setup
Status
Preview
Version
0.2.1
Package
VSIX
File size
267.61 KB
SHA-256
4ce0f47de6ce2776673d93d472bd22cadad70ffd6c8e90f0c6efea18d9c82a57

In this release

  • Installs in place over Forge 0.2.0 without requiring an uninstall. The extension ID, API key, and settings remain in place. Installing over Forge 0.1.0 through 0.1.3 keeps the same extension ID (devfoundry.forge-extension), API key, settings, and Project Memory.
  • Desktop Cursor exposes local editor storage as vscode-userdata. When that storage has no previous Forge knowledge store, Forge imports intact workspace transcripts instead of stopping.

Since Forge 0.1.3

These capabilities shipped in Forge 0.2.0 and are included in 0.2.1.

  • Forge Projects are engineering knowledge workspaces. A project is not a repository, a VS Code workspace, or a folder, and it can exist with no folder open. A local folder can be associated with a project.
  • Conversations, folders, tags, associations, and attachments are stored in the Forge knowledge directory on this machine, outside editor extension storage. They are not stored in .forge/ or the repository. Uninstalling the extension does not delete them. Unassigned conversations are not in a project yet. Opening another folder does not hide them.
  • The sidebar Conversations control is the everyday navigator. The Conversations organizer is the larger management surface. Organize with nested folders, search, project-specific tags, pin, archive, rename, move, and delete. Moving a conversation out of its project removes that project’s tags.
  • Attach images, PDFs, and supported text or source files. Choose them, drop them on the composer, or paste an image. They stay local until you send a message that includes them; that send transmits the selected files to the provider for the thread. Not every model accepts every file type.
  • Composer slash commands: /new, /conversations, /help, /model, /usage, and /key. They run locally and do not become reasoning turns.
  • A thread keeps its provider and model. Switching provider starts a new conversation and leaves the previous one in Conversations. /new and a provider-changing /model are refused while files are staged, so those files are not discarded.
  • Older workspace transcripts are imported once into this local store when no previous knowledge store remains. Project Memory and legacy planning files remain under .forge/.

What this preview includes

  • Ask — independent questions about the repository
  • Review — a second opinion on a coding agent’s plan or fix
  • Independent repository investigation, including git_diff, when a workspace folder is available
  • Forge Projects and Conversations in the local Forge knowledge directory
  • Attachments you choose to send with a message
  • Project Memory under .forge/
  • Coding-agent handoff via Copy as Instructions
  • Local conversation history and usage information
  • Bring your own OpenAI or Anthropic API key (VS Code Secret Storage)
  • Forge Help

Forge does not edit application source.

Forge 0.2.1 is available through the Visual Studio Marketplace, the Open VSX Registry, and direct VSIX download from forgedev.tools. The extension identifier is devfoundry.forge-extension.

Getting Started Privacy Support & Feedback Forge 0.1.3 Forge 0.1.2 Forge 0.1.1 Forge 0.1.0 Product overview