GuildForge AI
Sign in

Documentation

Concise guides for using GuildForge AI. Features labeled Desktop app only or Not available yet reflect current reality.

Getting started

GuildForge AI is a Windows desktop workspace for designing Discord servers and creating bots with local AI. Install the desktop app (Windows 10/11), create a GuildForge account, and connect Discord to manage servers you are authorized to administer.

  • Download and install the desktop app from the download section.
  • Ensure a local AI runtime is available if you want AI features; the app detects it and explains installation without silently downloading executables.
  • Sign in at /signin.html or in the app, then connect Discord.

Discord connection

GuildForge uses Discord's official authorization flow. You authenticate on Discord's site and grant permissions; GuildForge never asks for your Discord password.

  • From the dashboard, use Connect Discord to start authorization (GET /auth/discord/start).
  • GuildForge lists servers where you have permission to manage and indicates installation/configuration state.
  • GuildForge configures existing authorized servers via the official Discord API. It does not create servers through unsupported methods.

Server builder

The AI Discord Server Builder helps you describe a community structure and preview roles, channels, and permissions before applying changes. Applying changes uses the official Discord API and requires appropriate permissions on the selected server.

Server-building AI runs in the desktop app (local AI). The browser dashboard provides workspace visibility and cannot start a local AI session.

Bot projects

Bot projects are discord.js-based projects generated from prompts or starter templates (e.g. moderation, economy, welcome, tickets, leveling, utility). Projects include a file tree and revisions for review.

  • Create projects from the dashboard or desktop app. The browser view lists projects and details read-only.
  • Editing and running generated code is a desktop-app workflow; review files before execution.
  • Projects are plain code on disk in the desktop environment—no lock-in.

Local hosting

Available Free local hosting runs bots on your Windows PC through the desktop app.

  • Provides local process supervision, logs, restarts, and per-bot memory limits.
  • Bots stop when your PC sleeps, shuts down, loses internet, or the app/supervisor is terminated.
  • Local hosting is not guaranteed uptime hosting.

Cloud hosting Not available yet

Paid cloud hosting is planned but not provisioned and not for sale. When available, it will provide managed deployments subject to plan limits, quotas, and monitoring. No 100% uptime is claimed.

The dashboard shows honest empty/unavailable states for cloud hosting. Do not treat UI placeholders as active capacity.

Resource units

Resource units are a scheduling budget for allocating cloud capacity across projects. They are not unlimited resources.

  • Plans define total cloud resource units and max deployments (Free: 0/0, Starter: 100/3, Pro: 300/6, Business: 1000/20).
  • Allocations are submitted to the server (PUT /allocations) with optimistic versioning; the server validates and may reject invalid or conflicting changes.
  • Independent hard limits apply to memory, CPU, storage, and requests when enforced by the hosting runtime.

Security

  • Discord auth: official OAuth/authorization flow; no Discord passwords collected.
  • Tokens/secrets: sensitive tokens are not written into source files, logs, or exports. Cloud-only secrets are never embedded in the desktop app.
  • Permissions: request the narrowest Discord permissions needed for an operation.
  • Downloads: any installer execution requires a pinned version and verified SHA-256 manifest (policy); GuildForge must not silently execute installers.
  • Transparency: simulated or unavailable subsystems are labeled honestly.

Self-hosting the API

The GuildForge API is a Cloudflare Workers + D1 service (see infrastructure/cloudflare). To run or deploy your own instance:

  • Configure environment bindings: DB (D1), SESSION_SECRET, ENVIRONMENT, and ALLOWED_ORIGINS (comma-separated origins allowed for CORS with credentials).
  • Apply database migrations/schema for users, sessions, subscriptions, projects, allocations, and activity as required by the worker.
  • Set the website VITE_API_URL at build time (or rely on the fallback) so the frontend points to your API origin.
  • Use HTTPS in production and keep secrets out of client bundles and repositories.

This is an overview; consult the worker source and infrastructure configuration for authoritative routes and schema.