Keep your projects, tickets, and next steps together.

01 · Start here

Open the app and give it one project to track.

You can use project and ticket tracking without a Discord bot or an AI agent. If DevHub is already installed, go straight to your first project.

1. 1

   Download the current Windows package

   Use 64-bit Windows 10 or newer. Download the portable ZIP above and compare its SHA-256 with the displayed checksum.

2. 2

   Extract the complete ZIP

   Choose a writable folder and extract all files. Keep the application, runtime DLLs, notices, and licenses together. Do not run the app from inside the ZIP.

3. 3

   Launch DevHub

   Open devhub.exe in the extracted folder. The Dashboard is your starting point. A second launch focuses the existing window. A fresh database contains a path-free My Project starter entry you can edit or delete.

4. 4

   Locate your data and set backup retention

   Open Settings, then open data folder. This is where your private records live; the default is data\ beside the executable. Under Backups and portable exports, choose versions to retain and select Save maintenance settings.

Ready to use it? Add your project, save a ticket, and return to the Work Queue when you want to choose what to do next.

02 · Find your way

Each page has one clear job.

03 · Add a project

Start with only the information you actually have.

1. 1

   Name the project

   On the Dashboard, enter a name in new project name... and choose Add project. You can also edit the starter My Project entry.

2. 2

   Set its working path

   Open the project, then choose Edit project. Set working path to the folder you work in, such as C:\Projects\MyApplication, then choose Save. Use the project folder button to check that it opens the intended location.

3. 3

   Add optional discovery details

   Add a description or repository URL if useful. Aliases, version tracking, Discord visibility, and Codex skills can wait until you use those features. The Codex skills field names skills for copied packets; it does not install them.

4. 4

   Add commands only when ready

   Build, Prep, Release, and Version commands are project-specific. Empty commands stay hidden from the Dashboard.

04 · Manage work

Capture quickly, then add detail where it helps.

Try a first ticket

Create an Implementation titled Add a setup guide. In edit text, write what a new user should be able to do and how you will check it, then save. Use Work Queue to find it again. When work begins, change its status to in_progress; if a missing decision stops progress, use blocked and record what is needed. Add the result and verification before completing it.

Priority: P1 is low, P2 normal, P3 high, and P4 critical. Due date is a deadline; review again is when to revisit the item. In the ticket editor, contributor add/remove/credit actions save immediately.

05 · Optional project commands

Run each project's own workflow without memorizing commands.

1. 1

   Use a command that already works for the project

   Open Edit project. Put the project's real build command in build, its packaging command in prep release, its publication command in send release, or its version helper in update version. These scripts belong to your project; DevHub does not create them.

2. 2

   Check where it runs

   Commands run in working path unless working dir override is set. Quote script paths containing spaces. Save the project, select the relevant button, and read the console output if it fails.

Pipeline commands and their working folders come from the selected project's saved configuration. The local API does not accept a replacement command or working directory from a request.

06 · Hand work to AI

Copy the smallest packet that answers the question.

1. 1

   Paste the packet into the project session

   It includes IDs, details, evidence, workspace context, hashes, skill routing, and safety boundaries.

2. 2

   Record confirmed findings

   Put decisions, evidence, requested changes, blockers, and the next action back on the owning ticket or workflow.

3. 3

   Keep authority explicit

   A packet supplies context. It does not authorize edits, builds, publication, deployment, deletion, or a broader task.

07 · Optional Discord feedback

Review a suggestion before it becomes work.

1. 1

   Connect a bot you control

   Create a bot in Discord's developer portal, enable Message Content Intent, and invite it to your server with read/history access to the channels you want to monitor. Enter its token under Discord → Bot and choose Save token + connect.

2. 2

   Choose trusted administrators and monitors

   Enter numeric user IDs in the admin/developer whitelist and choose Save whitelist. Under Monitors, enter the server ID and optionally a channel ID, then select Add monitor. A server-only monitor covers every channel the bot can read.

3. 3

   Review the inbox

   Open Edit pending to refine the notes, title, type, priority, or project. Choosing a project enables Save as ticket, which promotes the suggestion. Use clear - keep pending and Save pending to save edits without promotion.

4. 4

   Choose what becomes a ticket

   Approve useful feedback or choose Save as ticket to create a credited ticket and fetch eligible attachments. Dismiss unwanted suggestions to change their DevHub review state; the original Discord message remains in Discord.

5. 5

   Correct attribution deliberately

   Use Credits → merge with when the same person has duplicate or mistaken identities.

08 · Keep durable context

Use the right record for the job.

09 · Protect your data

Back up your data folder and attachments.

In Settings → Backups and portable exports, choose Back up now for a database backup or Export Markdown + JSON for readable copies. Use the backups and exports buttons to open the results.

10 · Codex integration

Nine focused skills cover the common workflows.

Choose a skill by the outcome you want. All ten are distributed on XA Docs, separately from the GitHub application source. Install the complete bundle before trying the example requests.

11 · Optional AI setup

Install the skills, then check the connection.

The GitHub repository contains the application. XA Docs hosts the companion skills and their downloads. A skill tells Codex how to help with a task; DevHub must be running for the skill to read or update your records.

1. 1

   Download the complete bundle

   Download the ten-skill ZIP, or inspect individual packages in the skill library. Keep devhub-control alongside the workflow skills because it provides their connection to DevHub. Compare the ZIP checksum with the published value to verify the download.

2. 2

   Extract the skill folders into Codex

   For a standard Windows user installation, enter %USERPROFILE%\.agents\skills in File Explorer and create the folder if needed. Extract the ten devhub-* directories directly there, keeping every nested file. Check existing copies before replacing a skill you have customized. The result should include:

   %USERPROFILE%\.agents\skills\
   |-- devhub-control\
   |   |-- SKILL.md
   |   |-- agents\openai.yaml
   |   |-- references\api-contract.md
   |   `-- scripts\devhub.ps1
   |-- devhub-add-project\
   |   `-- SKILL.md
   `-- ...the remaining complete devhub-* folders

   Do not leave an extra xa-devhub-skills wrapper folder between skills and the individual directories. Follow the current Codex skill instructions if your setup uses another location.

3. 3

   Check that Codex sees them

   In Codex CLI or the IDE extension, open /skills or type $devhub-control. Skills are normally detected automatically; restart the Codex session if the new folders do not appear. Adding a name to DevHub's Codex skills project field alone does not install it.

4. 4

   Run a read-only connection check

   Start DevHub under the same Windows user. In Windows PowerShell, run:

   $skillRoot = Join-Path $env:USERPROFILE '.agents\skills'
   $dh = Join-Path $skillRoot 'devhub-control\scripts\devhub.ps1'
   powershell -NoProfile -ExecutionPolicy Bypass -File $dh -Action health

   A successful response confirms the client can reach DevHub. The client finds the current local credential automatically; do not paste API or Discord tokens into an AI prompt. The default needs no configuration file. See the control skill for a custom port or connection troubleshooting.

Try one clear request

Start with a read, then choose a specific task. Replace the example project with your own:

$devhub-control Check health and list projects without making changes.
$devhub-add-project C:\Projects\MyApplication
$devhub-cleanup-tickets My Project
$devhub-prioritize-tickets My Project

Run these as separate requests in Codex. Cleanup presents title and duplicate-merge proposals for approval. Prioritization currently returns ranking and title proposals only, because the public control API cannot yet update an existing ticket's priority. For a copied review bundle, ask $devhub-implementation-confirmer to review it; for implementation, give $devhub-development the exact task you want done.

12 · Keep your installation

Update the app while keeping your records.

1. 1

   Find and back up the complete data folder

   Use Settings → open data folder to locate it. Close DevHub, then copy that entire folder to a separate backup location, including any database companions and ticket-images or ticket-files directories.

2. 2

   Keep data separate from the replacement app files

   For a source build, retain your data while following the build instructions. If you have a portable binary package, extract all application files together and keep your existing data\ in place. Do not replace your records with an empty data folder from another installation.

3. 3

   Reopen and check your projects

   Confirm your project list and a recent ticket are present. If moving to another Windows profile or machine, protected credentials may need to be entered again; never assume copied credentials will decrypt there.

To use a different data folder, launch with devhub.exe --data-dir "D:\DevHubData". This selects a location; it does not copy your existing records. To uninstall, close DevHub, keep the data or exports you want, and remove its application folder.

Help when something fails

Check the symptom and the next step.

For a problem that remains, record the DevHub version, the action you took, the expected result, and the relevant error text. Remove private project details and credentials before opening a GitHub issue. Use the security policy for vulnerabilities.

13 · Advanced inspection

Browse the reviewed XA DevHub 1.0.6 source snapshot.

The code viewer exposes every file in the privacy-curated c49030f snapshot with its exact size, SHA-256 value, copy action, and individual download. The manifest contains — files.