ClaudeForge: baixar versions anteriors

## Downloads

| Platform | Architecture | File |
|-----------------------|----------------|----------------------------------------------------------------------------|
| Windows | x64 | `ClaudeForge-win-x64.zip` |
| Windows | ARM64 | `ClaudeForge-win-arm64.zip` |
| Linux | x64 | `ClaudeForge-linux-x64.tar.gz` |
| Linux | ARM64 | `ClaudeForge-linux-arm64.tar.gz` |
| macOS (Intel) | x64 | `ClaudeForge-osx-x64.tar.gz` |
| macOS (Apple Silicon) | ARM64 | `ClaudeForge-osx-arm64.tar.gz` |

The version (2026.3.922) is encoded in the release tag rather than in
the archive filenames — publish.ps1 produces unversioned artefact names
so local dev builds and CI builds share one filename pattern.

**Linux:** Extract, then run the bundled `linux-setup.sh` to install a per-user `.desktop` entry so Wayland compositors render the window icon correctly:
```bash
tar -xzf ClaudeForge-linux-x64.tar.gz -C ~/ClaudeForge
cd ~/ClaudeForge
./linux-setup.sh
./ClaudeForge
```

**macOS:** The binary is unsigned. Use the bundled `allow-app-to-run.sh` to strip the Gatekeeper quarantine xattr from every file in the extracted directory:
```bash
tar -xzf ClaudeForge-osx-arm64.tar.gz -C ~/ClaudeForge
cd ~/ClaudeForge
./allow-app-to-run.sh
./ClaudeForge
```

---

## What's Changed

### Added

- **Claude Opus 5.5.** The model picker and the `model` suggestion list now carry Opus 5.5
(`claude-opus-5-5`), and the `opus` alias resolves to it. Opus 5 keeps its row and stays
pinnable as an exact snapshot; it simply leaves the default picker and gives up the alias.
**Opus 5.5 defaults to `medium` effort rather than `high`** - the only model in the current
lineup whose default differs - which is recorded in the catalog and is what an unrecognized
effort value now coerces toward under `opus`.

### Fixed

- **Enterprise policy is read from the directory Claude Code actually reads it from.**
ClaudeForge looked for `managed-settings.json` in `~/.claude/`; Claude Code reads it from a
per-OS *system* directory - `C:\Program Files\ClaudeCode\` on Windows,
`/Library/Application Support/ClaudeCode/` on macOS, `/etc/claude-code/` on Linux and WSL.
It failed both ways and silently: a machine with real policy showed **no managed layer**, so
the effective view told you your own value won where policy actually overrides it; and a file
you placed at `~/.claude/managed-settings.json` displayed as enforced while doing nothing.
`managed-mcp.json` is now handled as well.
- **`CLAUDE_CONFIG_DIR` is honoured.** The app documented this variable in its own tooltips and
then ignored it, so anyone who had relocated their Claude home was shown - and was editing -
the settings in `~/.claude` instead. Every path derived from the home now resolves through it,
including the ones behind the Memory and Agents & Skills pages, which previously read a
different tree than the settings pages did. `~/.claude.json` is deliberately unaffected: it
sits beside the home rather than inside it, so Claude Code does not move it either.
- **The restore progress bar no longer names `~/.claude/` when the home is somewhere else.**
The label said `Restoring ~/.claude/...` in all nine languages regardless of where the restore
was actually writing.

## Downloads

| Platform | Architecture | File |
|-----------------------|----------------|----------------------------------------------------------------------------|
| Windows | x64 | `ClaudeForge-win-x64.zip` |
| Windows | ARM64 | `ClaudeForge-win-arm64.zip` |
| Linux | x64 | `ClaudeForge-linux-x64.tar.gz` |
| Linux | ARM64 | `ClaudeForge-linux-arm64.tar.gz` |
| macOS (Intel) | x64 | `ClaudeForge-osx-x64.tar.gz` |
| macOS (Apple Silicon) | ARM64 | `ClaudeForge-osx-arm64.tar.gz` |

The version (2026.3.916) is encoded in the release tag rather than in
the archive filenames — publish.ps1 produces unversioned artefact names
so local dev builds and CI builds share one filename pattern.

**Linux:** Extract, then run the bundled `linux-setup.sh` to install a per-user `.desktop` entry so Wayland compositors render the window icon correctly:
```bash
tar -xzf ClaudeForge-linux-x64.tar.gz -C ~/ClaudeForge
cd ~/ClaudeForge
./linux-setup.sh
./ClaudeForge
```

**macOS:** The binary is unsigned. Use the bundled `allow-app-to-run.sh` to strip the Gatekeeper quarantine xattr from every file in the extracted directory:
```bash
tar -xzf ClaudeForge-osx-arm64.tar.gz -C ~/ClaudeForge
cd ~/ClaudeForge
./allow-app-to-run.sh
./ClaudeForge
```

---

## What's Changed

### Fixed

- **Skill and agent descriptions were often wrong, blank, or literally `>-`.** The
front-matter parser understood plain and quoted scalars, inline and block lists —
and nothing else. Every other shape that occurs in real skill files read back as
the wrong value. Three shapes mattered, found by surveying all 236 front-matter
files under `~/.claude`:
- **Folded and literal block scalars** (`description: >-`, `description: |`).
Nearly every skill Claude Code ships writes its description this way, because
the prose contains quotes and colons a plain scalar would have to escape. The
header token was read as the value, so the Agents & Skills list, the detail
pane and the editor all showed `>-`.
- **Multi-line flow scalars** — a value carried across indented lines with no
block indicator at all. Nothing follows the colon in that form, so the value
read as empty and the prose fell through as unparsed filler. Anthropic's own
`math-olympiad` plugin skill showed **"(no description)"**.
- **Nested mappings** (`metadata:` with indented keys beneath it) were flattened
into phantom top-level fields, and writing one re-rendered it at column 0 —
silently lifting it out of its parent. A mapping is now consumed whole and
re-emitted verbatim.

All three chomping indicators (`-`, `+`, none) and explicit indentation
indicators are handled. A description carrying newlines is flattened for the list
row, which is a single ellipsised line; the detail pane and editor keep the real
multi-line value.

- **Editing one description reformatted the whole file.** An edited field now keeps
the shape it arrived in — a folded description is written back folded, and a
value spread over several lines stays spread over several lines rather than
collapsing into one very long plain line.

- **Saving a Windows skill file rewrote its line endings.** Parsing stripped the
`\r` from each line, so a CRLF file whose block scalar came back untouched was
written out with LF inside the block and CRLF everywhere else. Opening a file and
saving it with no edits left it with mixed line endings.

- **Deep links into a tab only worked on one page.** Only Agents & Skills could
consume a tab segment; every settings page — Hooks, Permissions, General, all of
them — silently dropped it and landed on whichever tab it defaulted to, and never
persisted a tab, so place-keeping could not bring one back either.
`--deep-link claude-code/permissions/properties` had been documented as working
the whole time. Settings pages, Effective Settings and Backup / Restore now all
round-trip their tab, and a tab contributed by the per-group customizer addresses
exactly like a built-in one — `--deep-link claude-code/hooks/hooks.flow` opens the
Hooks fl

## Downloads

| Platform | Architecture | File |
|-----------------------|----------------|----------------------------------------------------------------------------|
| Windows | x64 | `ClaudeForge-win-x64.zip` |
| Windows | ARM64 | `ClaudeForge-win-arm64.zip` |
| Linux | x64 | `ClaudeForge-linux-x64.tar.gz` |
| Linux | ARM64 | `ClaudeForge-linux-arm64.tar.gz` |
| macOS (Intel) | x64 | `ClaudeForge-osx-x64.tar.gz` |
| macOS (Apple Silicon) | ARM64 | `ClaudeForge-osx-arm64.tar.gz` |

The version (2026.3.901) is encoded in the release tag rather than in
the archive filenames — publish.ps1 produces unversioned artefact names
so local dev builds and CI builds share one filename pattern.

**Linux:** Extract, then run the bundled `linux-setup.sh` to install a per-user `.desktop` entry so Wayland compositors render the window icon correctly:
```bash
tar -xzf ClaudeForge-linux-x64.tar.gz -C ~/ClaudeForge
cd ~/ClaudeForge
./linux-setup.sh
./ClaudeForge
```

**macOS:** The binary is unsigned. Use the bundled `allow-app-to-run.sh` to strip the Gatekeeper quarantine xattr from every file in the extracted directory:
```bash
tar -xzf ClaudeForge-osx-arm64.tar.gz -C ~/ClaudeForge
cd ~/ClaudeForge
./allow-app-to-run.sh
./ClaudeForge
```

---

## What's Changed

Claude Fable 5.1 (`claude-fable-5-1`) is the current Fable build, so the `fable`
alias now resolves to it and Fable 5 becomes a legacy-but-still-pinnable row.
Verified against the models overview rather than recall — Fable 5 is listed
under "Legacy models (still available)".

Followed the AGENTS.md / docs/MODEL-CATALOG.md "new model launch" playbook:

- model-catalog.json — new `claude-fable-5-1` row (1M context, effort low..max
incl. ultracode, default `high`, auto-mode capable, copied from the outgoing
build); `alias: "fable"` moved onto it; `aliases.fable` repointed; the previous
holder demoted to `legacy: true, alias: null` (row kept — still a valid pin).
Invariant preserved: exactly one non-legacy row per family alias.
- claude-code-settings.overlay.json — AutoCompleteBox suggestion and the
`model.description` example swapped to the new snapshot id.
- enumdescriptions.json — added the 5.1 pin tooltip, refreshed the `fable` and
`best` tooltips, and REPLACED the old pin row rather than accumulating it.
`model.examples` <-> tooltip keys are exactly 1:1 (11/11, no orphans).

No test change needed: ModelCatalogTests only hardcodes the `opus` alias target.
The bundled JSON schema is untouched — schemastore.org omits model names, so
`refresh-schema` is never the mechanism that adds a model (a dry run confirms
zero content changes; PR #33 already brought the schema current).

Docs: both playbooks now name where to verify model facts
(platform.claude.com models overview) and warn that a family can supersede
itself within a generation — Fable 5 -> 5.1 is not a whole-number bump. That
lookup was the one step being re-derived every session.

Verified: validate-model-catalog.ps1 passes (models=9, aliases=4); full suite
2708 passed / 11 skipped / 0 failed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

## Downloads

| Platform | Architecture | File |
|-----------------------|----------------|----------------------------------------------------------------------------|
| Windows | x64 | `ClaudeForge-win-x64.zip` |
| Windows | ARM64 | `ClaudeForge-win-arm64.zip` |
| Linux | x64 | `ClaudeForge-linux-x64.tar.gz` |
| Linux | ARM64 | `ClaudeForge-linux-arm64.tar.gz` |
| macOS (Intel) | x64 | `ClaudeForge-osx-x64.tar.gz` |
| macOS (Apple Silicon) | ARM64 | `ClaudeForge-osx-arm64.tar.gz` |

The version (2026.3.810) is encoded in the release tag rather than in
the archive filenames — publish.ps1 produces unversioned artefact names
so local dev builds and CI builds share one filename pattern.

**Linux:** Extract, then run the bundled `linux-setup.sh` to install a per-user `.desktop` entry so Wayland compositors render the window icon correctly:
```bash
tar -xzf ClaudeForge-linux-x64.tar.gz -C ~/ClaudeForge
cd ~/ClaudeForge
./linux-setup.sh
./ClaudeForge
```

**macOS:** The binary is unsigned. Use the bundled `allow-app-to-run.sh` to strip the Gatekeeper quarantine xattr from every file in the extracted directory:
```bash
tar -xzf ClaudeForge-osx-arm64.tar.gz -C ~/ClaudeForge
cd ~/ClaudeForge
./allow-app-to-run.sh
./ClaudeForge
```

---

<!-- Release notes generated using configuration in .github/release.yml at v2026.3.810 -->

## What's Changed
- **Filter on the Agents & Skills page** — narrows all three segments
(Sub-agents / Skills / Slash Commands) by artifact name, description, or source,
with a match count and a clear button. Section headers drop out when their group
has no surviving row, so there are no orphan "Yours" / "Plugin" labels above
nothing. Long lists no longer have to be scrolled to find a known item.
- **Deep links (`--deep-link <path>`)** — launch straight into a page, tab, or
item: `--deep-link claude-code/permissions`,
`--deep-link agents-skills/skills/pdf`. The grammar is
`page[/tab][/item]` (or `product/page[/…]`), keyed on new stable
`NavigationNodeViewModel.NodeId` identifiers rather than display labels, so a
link keeps resolving in any language. A deep-linked item is revealed by
filtering the list to it, with the filter box outlined to show the narrowing
came from navigation. An unresolvable path is logged and ignored — it never
blocks launch. See the README "Deep links" section.
- **"Copy deep link"** on the Agents & Skills detail toolbar — puts a ready-to-use
`--deep-link` path for the open artifact on the clipboard, fully qualified as
`name@source`, so nobody has to derive an id by hand (and a path can be pasted into
a ticket or a runbook). A malformed `--deep-link` now reports itself on the terminal
with the valid pages listed instead of failing silently — the binary is a `WinExe`,
so it attaches to the parent console to do it — and a well-formed-but-unresolvable
path raises a status-bar warning. An unresolvable *persisted* path stays quiet,
since that is routine after deleting an artifact.
- **Your place is kept below the page level** — the active tab and open item are
persisted (`WindowState.lastDeepPath`) and restored on relaunch, instead of only
the page. **Reload Window** restores the full state, including an edit in
progress (see Fixed). Reusable via the new `IDeepNavigable` contract; the
Agents & Skills page is the first adopter.

## New Contributors
* @JanusMael made their first contribution in https://github.com/JanusMael/ClaudeForge/pull/28

**Full Changelog**: https://github.com/JanusMael/ClaudeForge/compare/v2026.3.724...v2026.3.810