QuireForge

Build boldly. Work locally.

Important

QuireForge is an unofficial community project. It is not made, endorsed, supported, or distributed by OpenAI.

QuireForge is a native Linux workspace for planning and supervising AI-assisted software development with Codex. It keeps user-selected projects in place, uses documented interfaces, and keeps QuireForge metadata separate from Codex authentication, configuration, and session data.

The canonical desktop identifier is io.github.codeframe78.QuireForge; the static project site is quireforge.jamesjennison.net.

What QuireForge provides

• A Tauri desktop workspace built with Rust, React, TypeScript, and Vite.
• Managed Codex account onboarding and bounded native conversation workflows.
• User-selected project attachment, reviewed Git and worktree workflows, and a native integrated terminal with explicit controls.
• Read-only normalized Project State evidence and a managed, transient Advisor workspace with explicitly confirmed temporary context and a closed bounded collection of text/data, image, PDF, ZIP-manifest, or static-ELF metadata attachments: up to three entries and at most one image.
• Accessible routed workspaces, local appearance preferences, and reproducible Ubuntu 22.04 Debian candidate validation.
• A QuireForge task workbench shell with a primary conversation surface, an opt-in context drawer, safe navigation actions, and a collapsed view of the existing managed terminal; it adds no new execution authority.
• A bounded local task catalogue with user-controlled titles, organizational status, archive/restore, explicit deletion, and up to four visible alternate plans. Task records retain no conversation, path, attachment history, or execution authority.
• Governed context review with explicit local selection, deterministic private redacted assembly, bounded review, and one-use fictional local-only delivery; it is not provider transmission, inference, credential, connector, browser, MCP, automation, or mutation authority.
• A bounded transient Advisor conversation surface with independently scrollable replies, reader-controlled follow-latest, and an optional safe details drawer; it adds no Advisor authority or persistence.

The current implementation status, completed milestones, known limitations, and next approved work are maintained in Current State.

Safety boundaries

• QuireForge does not collect passwords, browser cookies, session tokens, or API keys for Codex or ChatGPT authentication.
• The frontend uses narrow typed native commands; it does not spawn arbitrary processes or consume raw Codex protocol messages.
• Project operations are scoped to attached directories and explicit user actions. Detach, archive, and remove actions are not filesystem deletion.
• Advisor remains non-executable. Its approved B2 controller can hand one explicit, expiring, digest-bound request to the separate project execution workspace only after immediate revalidation; Advisor itself cannot run shell, terminal, Git, repository, or automatic execution actions. Optional Project State context still requires explicit selection and per-send confirmation.
• The project does not scrape ChatGPT, reverse engineer private protocols, or imply OpenAI endorsement.

See the architecture, threat model, and Codex integration findings for the detailed boundaries.

Quick start

Use a Linux host with the supported Node, pnpm, Rust, Tauri, Python, and Git prerequisites described in Building.

pnpm install --frozen-lockfile
pnpm validate
pnpm test:e2e
pnpm desktop:dev

pnpm validate is the full non-browser quality gate. pnpm test:e2e adds the desktop browser and accessibility coverage. See Testing for targeted checks and Building for the pinned Ubuntu 22.04 package workflow.

Repository layout

Path	Purpose
apps/desktop/	Tauri desktop application, Rust core, React UI, and desktop tests
apps/website/	Static Astro website
docs/	Architecture, decisions, milestone evidence, and operating guidance
scripts/	Repository, package, and release-validation utilities
assets/brand/	QuireForge brand sources and usage guidance

Documentation

Start with the documentation index. The most common references are:

• Current State and Roadmap
• Architecture and decisions
• Building, Testing, and Releasing
• Compatibility, Website, and Changelog
• Milestone evidence, forecasts, and time ledger

Contributing and support

QuireForge is licensed under the Apache License 2.0. Read Contributing, the Code of Conduct, and the security policy before opening a contribution or report. For project-status expectations and sanitized diagnostics guidance, see Support.