Skip to content

Add LocalForge#2221

Open
lkjhgfdsallx wants to merge 1 commit into
electron:mainfrom
lkjhgfdsallx:main
Open

Add LocalForge#2221
lkjhgfdsallx wants to merge 1 commit into
electron:mainfrom
lkjhgfdsallx:main

Conversation

@lkjhgfdsallx

Copy link
Copy Markdown

Pull Request draft — add LocalForge to electron/apps

Target: https://github.com/electron/apps
Branch: add-localforge
Title suggestion: Add LocalForge


Copy into GitHub PR description (official template filled)

<!--
Thank you for your PR!
Please take a moment to complete this guide, it helps us to understand the objective of your PR and makes it easier to review.
If you're not adding a new application, you can skip the following.
-->

## Adding a new application

### Checklist

- [x] I have read and completed the checklist of [Submission Guide](https://github.com/electron/apps/blob/master/contributing.md#submission-guidelines)
- [x] My application is open-source and has been created for at least 20 days
- [ ] My application is closed-source and here is a proof it uses Electron:

<!--
Open-source application — closed-source proof not applicable.
Electron usage is visible in package.json (electron ^33) and the public repository.
-->

### Description

**LocalForge** is a local-first AI desktop workbench built with **Electron 33**, React 19, and TypeScript.

Users keep API keys and data on their own machine: multi-provider chat, agents (ReAct / plan-and-execute), local knowledge base with embeddings, workspace file/terminal tools, and MCP extensions. No account or forced cloud intermediary.

**Tagline:** Forge AI. Locally. Privately.

#### Links

| | URL |
|--|-----|
| **Website / source** | https://github.com/lkjhgfdsallx/electron-aitool |
| **Latest downloads** | https://github.com/lkjhgfdsallx/electron-aitool/releases/latest |
| **v1.0.0 release** | https://github.com/lkjhgfdsallx/electron-aitool/releases/tag/v1.0.0 |
| **License** | [MIT](https://github.com/lkjhgfdsallx/electron-aitool/blob/main/LICENSE) |
| **README** | https://github.com/lkjhgfdsallx/electron-aitool#readme |

#### Electron proof (open source)

- Desktop shell: **Electron 33** via `electron-vite` + `electron-builder`  
  - [`package.json`](https://github.com/lkjhgfdsallx/electron-aitool/blob/main/package.json)`"electron": "^33.3.1"`  
  - [`electron-builder.yml`](https://github.com/lkjhgfdsallx/electron-aitool/blob/main/electron-builder.yml)`appId: com.localforge.app`, productName **LocalForge**  
  - Main process: [`electron/main/`](https://github.com/lkjhgfdsallx/electron-aitool/tree/main/electron/main)
- Cross-platform packaging: Windows (NSIS), macOS (DMG), Linux (AppImage)

#### Platforms

- Windows · macOS · Linux  
- Prebuilt installers on GitHub Releases (see release assets for the exact files shipped in each tag)

#### Why it fits electronjs.org/apps

- Real end-user desktop product (not a template or demo)
- Public MIT source + installable releases
- Clear product identity (LocalForge) with icon and documentation
- Privacy / productivity category: local-first AI workbench

#### Screenshots

Please attach these from the product repo when opening the PR (GitHub upload):

1. **Smart chat / Agent**`build/DialogueScreenshot.png`  
2. **Workspace**`build/WorkspaceScreenshot.png`  
3. **Settings**`build/SettingScreenshot.png`

*(If you cannot attach files in the description, drag them into the PR conversation after opening.)*

#### App entry in this PR

- `apps/localforge/` — metadata YAML + icon (per submission guidelines)

Happy to adjust naming, category, or metadata if review requests changes. Thanks for maintaining the apps list!

PR title (short)

Add LocalForge

Alternate (if you prefer more context):

Add LocalForge — local-first AI desktop workbench

Tips to raise acceptance odds

  1. Only check open-source boxes — leave closed-source unchecked (already done above).
  2. Confirm repo age ≥ 20 days before submit; if the GitHub repo is younger than 20 days, wait or the checklist claim may be rejected.
  3. Upload 2–3 real screenshots in the PR (reviewers care more than long text).
  4. Ensure Release assets open and match platforms you claim.
  5. Do not paste this whole file into the repo — only the fenced “Copy into GitHub PR description” block goes into the PR body.
  6. After opening, reply to CI failures quickly (icon size / YAML schema are common).

Optional one-line commit message (already on your branch)

Add LocalForge

@lkjhgfdsallx
lkjhgfdsallx requested review from a team and Toinane as code owners July 21, 2026 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant