Repository navigation
Releases
Forge 0.6.1
Forge 0.6.1
Forge 0.6.1 completes the Forge Remote phone experience, aligns the bundled
browser with the native client, and makes forge the canonical executable
without breaking existing grok installations.
Forge Remote parity
The browser and native clients now share the same typed remote protocol for
streamed transcript updates, compact work disclosures, queued-message control,
model and reasoning changes, Fast Mode, usage, attachments, and same-directory
new sessions. The browser presentation mirrors the native thread and grouped
project views, while capability and session checks keep every action bound to
the exact terminal session.
The iOS client includes multiline composer sizing, separate Photos and Files
pickers, rotated-bearer deduplication, immediate scanner dismissal after a
validated pairing, compact work rows, and the updated Forge visual system.
Installation and updates
The packaged executable is now named forge. Installers, release archives,
source builds, test harnesses, and documentation use that canonical name while
retaining grok as a compatibility alias. A plain forge update or
grok update downloads the latest checksummed release and preserves existing
configuration, authentication, sessions, and memory under ~/.grok/.
This release also makes protobuf dependency discovery portable on Windows so
all advertised release targets can be built by the release workflow.
Supported platforms
- macOS Apple Silicon (
aarch64-apple-darwin) - Linux ARM64 (
aarch64-unknown-linux-gnu) - Windows x86-64 (
x86_64-pc-windows-msvc)
Install or update
curl -fsSL https://raw.githubusercontent.com/exaforge/forge/main/scripts/install | shOn Windows:
irm https://raw.githubusercontent.com/exaforge/forge/main/scripts/install.ps1 | iexExisting installations can update after the release artifacts finish
publishing:
forge updateChecksums are published beside every release archive. Native iOS source-build
instructions remain in
clients/forge-mobile/README.md.
Forge 0.5.0
Forge 0.5.0
Forge 0.5.0 adds a private phone client for an exact live Forge terminal
session. It keeps the terminal authoritative while making the session usable
from the bundled browser or the optional native iOS app over Tailscale.
Forge Remote
Running /rc creates a short-lived, tailnet-private HTTPS route and opens a
compact QR modal. The phone receives the existing transcript and live state and
can send prompts, stop cancellable work, ask /btw questions, change the model
or reasoning effort, inspect usage, manage queued work and plans, and answer
interactive approval or input cards when the session advertises those
capabilities. /rc stop revokes only the current session's pairing.
Several TUI sessions can expose separate pairings at once. Commands are bound
to the exact agent, canonical session, binding epoch, and gateway generation.
The latest authenticated foreground client owns each pairing, so moving between
Safari and Forge Mobile transfers control without command duplication or stale
socket mutation.
Browser and iOS clients
The bundled browser uses the pinned T3 Code visual source as a documented web
adaptation, with Basier Square typography, mobile-safe keyboard geometry, a
single Send/Stop action, /btw recognition, typed interaction cards, and
authoritative model, reasoning, and usage controls.
Forge Mobile retains the pinned MIT-licensed T3 Code native presentation layer
and replaces its cloud controller with Forge's private protocol. It includes
SecureStore pairings, native QR scanning, session switching, foreground
ownership transfer, native safe-area and keyboard behavior, and an embedded
Release bundle that does not require Metro. Its source workspace includes a
verified local installer for free Apple personal-team signing; no paid
TestFlight or App Store account is required for a developer to install their
own build on their own iPhone.
Reliability and security
Capability URLs contain a fresh 256-bit secret, remain private to Tailscale,
expire after eight hours, and are never accepted from the phone as a session
selector. Commands, asynchronous usage results, interaction responses, and
reconnects are validated against server-owned session and generation state.
Bounded channels, monotonic revisions, full-snapshot recovery, lifecycle
serialization, exact Tailscale route cleanup, and last-client ownership prevent
stale or cross-session control.
This release also makes local billing and free-usage cards dismissible with
Escape, preserves prompt drafts, fixes iOS scanner linkage and dark-mode text
contrast, and keeps the phone composer visible above the iOS keyboard.
Install or update
curl -fsSL https://raw.githubusercontent.com/DeveshParagiri/forge/main/scripts/install | shExisting installations can update after release artifacts finish publishing:
grok updateChecksums are published beside the macOS Apple Silicon, Linux x86-64, and Linux
AArch64 archives. Native iOS source-build instructions are in
clients/forge-mobile/README.md.
Forge 0.4.0
Forge 0.4.0
Forge 0.4.0 is synchronized with Grok Build 1.0.0 while preserving Forge's provider isolation, provider-aware controls, Fast Mode, external harnesses, session behavior, branding, and upstream synchronization tooling.
Provider-aware usage
Forge now integrates Grok Build's nonce-protected usage modal with provider-specific account usage:
- SpaceXAI sessions use native xAI billing.
- ChatGPT Codex sessions fetch Codex quota directly without calling xAI billing APIs.
- OpenRouter, custom, and unresolved providers fail closed with provider-appropriate availability text.
- Stale asynchronous responses cannot overwrite a newer or reopened usage modal.
Subscription upgrade surface
The dashboard-header xAI subscription upgrade CTA is now shown only for SpaceXAI sessions. ChatGPT Codex, OpenRouter, custom, and not-yet-resolved providers no longer receive an irrelevant xAI upgrade prompt.
External harness lifecycle
External Claude Code and Codex CLI process groups are enrolled in the owning session's process scope. Session teardown now reaps those children, and late launches are rejected if their owning session is already closing.
Upstream synchronization
This release incorporates Grok Build 1.0.0's session, usage, MCP, workspace, prompt queue, replay, terminal, and reliability improvements while retaining Forge's narrow provider and orchestration extensions.
Supported platforms
- macOS Apple Silicon (
aarch64-apple-darwin) - Linux x86_64 (
x86_64-unknown-linux-gnu) - Linux AArch64 (
aarch64-unknown-linux-gnu)
Install or update
curl -fsSL https://raw.githubusercontent.com/DeveshParagiri/forge/main/scripts/install | shExisting installations can update after release artifacts finish publishing:
grok updateChecksums are published beside every archive. See CHANGELOG.md for the complete Forge release history.
Forge 0.3.2
Full Changelog: forge-v0.3.1...forge-v0.3.2
Forge 0.3.1
Full Changelog: forge-v0.3.0...forge-v0.3.1
Forge 0.3.0
Forge 0.3.0
Forge 0.3.0 is synchronized with Grok Build 0.2.112. This release simplifies Forge's provider architecture while preserving ChatGPT subscription-backed Codex models, provider-aware controls, and external Claude Code and Codex CLI harnesses.
Provider architecture
Generic third-party providers now use upstream [model_providers.*] configuration and credentials. Forge no longer maintains a parallel [provider.*] configuration format, provider key store, status layer, or provider-login interface.
ChatGPT subscription support remains available through a narrow compatibility layer. Forge reads Codex OAuth data from ~/.codex/auth.json only for the canonical ChatGPT Codex endpoint. Fast Mode remains session-scoped and sends service_tier = "priority" only for models that explicitly support it.
OpenRouter and other generic providers use ordinary upstream API-key or environment-key configuration. Forge does not store their credentials.
Endpoint and data isolation
Provider-specific behavior now fails closed:
- xAI bearer tokens and private request metadata are stripped from unknown, cleartext, proxy, and third-party endpoints.
- Codex OAuth-file fallback cannot be activated by merely reusing the expected environment-key name on another endpoint.
- ChatGPT Codex Responses requests always send
store = false. - Cross-provider history drops opaque reasoning and flattens backend-only tool calls while retaining portable conversation context.
Codex compatibility
- Streamed reasoning summaries preserve indexed part boundaries, preventing adjacent Markdown sections from rendering as glued text.
- Credential reload resolves the complete active model, including provider defaults and model overrides.
- Provider-aware
/usage, reasoning-effort controls, and Claude Code/Codex CLI harness integrations remain supported.
Upstream synchronization
This release includes Grok Build 0.2.112 improvements such as faster nonblocking startup, bounded memory during large session replay, corrected plan-mode ordering, improved /loop termination prompts, configurable subagent nesting, leader-process sandboxing, and cleaner background-task snapshots.
Migration
Replace legacy Forge provider configuration with upstream provider entries:
[model_providers.openrouter]
base_url = "https://openrouter.ai/api/v1"
env_key = "OPENROUTER_API_KEY"Model entries select the provider with model_provider. Run codex login to populate or refresh ChatGPT Codex OAuth credentials.
Supported platforms
- macOS Apple Silicon (
aarch64-apple-darwin) - Linux x86_64 (
x86_64-unknown-linux-gnu) - Linux AArch64 (
aarch64-unknown-linux-gnu)
Install or update
curl -fsSL https://raw.githubusercontent.com/DeveshParagiri/forge/main/scripts/install | shExisting installations can update after release artifacts finish publishing:
grok updateChecksums are published beside every archive. See CHANGELOG.md for the complete Forge release history.
Forge 0.2.109.1
What's Changed
- chore: sync upstream Grok Build by @DeveshParagiri in #1
New Contributors
- @DeveshParagiri made their first contribution in #1
Full Changelog: forge-v0.2.0...forge-v0.2.109.1
Forge 0.2.105.1
Full Changelog: https://github.com/DeveshParagiri/forge/commits/forge-v0.2.105.1
Forge 0.2.0
Forge 0.2.0
Forge 0.2.0 is synchronized with Grok Build 0.2.106 and expands Forge's
multi-harness workflow, shortcut architecture, and adaptive orchestration
memory.
External sessions in /sessions
Saved Claude Code and Codex CLI sessions can now appear directly in the
/sessions dashboard. External sessions remain opt-in:
[sessions]
show_external = trueThe existing [compat.claude].sessions and [compat.codex].sessions settings
remain per-harness kill switches. Cursor sessions are not included in this
release.
Each external row identifies its harness once on the secondary line as
Claude Code or Codex CLI. Duplicate title badges and foreign HEAD branch
markers have been removed. Selecting an external row creates a fresh Forge
session and invokes /resume-claude <id> or /resume-codex <id>; Forge never
passes a foreign native ID through ACP session/load.
Extensible prompt shortcuts
Prompt shortcuts now resolve through an extensible action registry.
Shift+Tab consistently cycles the active model's supported reasoning-effort
levels across color themes, and the help/footer labels use the same binding
metadata as dispatch.
Adaptive orchestration memory
When memory is enabled, the existing flush and consolidation flow can learn
durable preferences about which models, external harnesses, and orchestration
patterns fit different tasks. This extends the existing semantic memory flow;
it does not add a separate preference database.
Maintenance and release reliability
- Forge's embedded user guide now documents capability-aware, cost-conscious
orchestration and the Forge-specific shortcut behavior. - A scheduled workflow can prepare daily upstream synchronization pull requests
without rewriting published history. - Release publication checks out the tagged source before downloading build
artifacts, preventing checkout cleanup from deleting release archives.
Supported platforms
- macOS Apple Silicon (
aarch64-apple-darwin) - Linux x86_64 (
x86_64-unknown-linux-gnu) - Linux AArch64 (
aarch64-unknown-linux-gnu)
Install or update
curl -fsSL https://raw.githubusercontent.com/DeveshParagiri/forge/main/scripts/install | shExisting installations can update after the release finishes publishing:
grok updateChecksums are published beside every archive. See
CHANGELOG.md for the complete Forge release history.
Forge 0.1.0
Forge 0.1.0
Forge 0.1.0 is the first release under Forge's independent semantic-versioning
scheme. It is synchronized with Grok Build 0.2.105.
Highlights
- More models: use SpaceXAI, ChatGPT Codex, and OpenRouter models from one
terminal interface. - Multi-harness subagents: delegate work across native roles, Claude Code,
and Codex CLI while retaining Forge's streaming, cancellation, metadata, and
resume experience. - Simpler Forge interface: consistent Forge branding and a cleaner default
theme. - Packaged updates:
grok updatedownloads a checksummed release binary and
replaces the installed executable atomically without touching~/.grok/
configuration, authentication, or sessions.
Fast mode indicator
Codex /fast remains capability-driven and provider-aware. When enabled, the
model label now uses the text-presentation lightning symbol ⚡︎ rather than
a colored emoji, so it follows the active terminal theme.
External sessions
External harness sessions are hidden by default. To show locally available
Claude Code and Codex sessions under /sessions, add:
[sessions]
show_external = trueRows are labeled Claude Code or Codex. Selecting one starts a fresh Forge
session and invokes /resume-claude <id> or /resume-codex <id> to import the
useful continuation context.
Supported release platforms
- macOS Apple Silicon (
aarch64-apple-darwin) - Linux x86_64 (
x86_64-unknown-linux-gnu) - Linux AArch64 (
aarch64-unknown-linux-gnu)
Intel macOS is intentionally not published.
Install or update
curl -fsSL https://raw.githubusercontent.com/DeveshParagiri/forge/main/scripts/install | shExisting Forge installations can update with:
grok updateChecksums are published beside every archive. On macOS, the installer ad-hoc
signs and verifies the installed executable.
Architecture and maintenance
Substantive fork behavior lives in additive, crate-local forge/ modules.
Upstream-owned files contain only narrow integration hooks. Forge development is
integrated on dev, validated and fast-forwarded to main, and synchronized
explicitly with upstream/main outside the end-user update path.
See CHANGELOG.md for the complete Forge change history.