Elgato_dark/Archon
1
0
Fork 0
mirror of https://github.com/coleam00/Archon synced 2026-04-21 13:37:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Merge pull request #966 from dynamous-community/fix/issue-965-setup-spawn-ux

Browse source 
ux: setup spawn failure as natural handoff, not error
This commit is contained in:
Cole Medin 2026-04-02 13:37:22 -07:00 committed by GitHub
commit 0cb45400ed
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 26 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
.claude/skills/archon/guides/setup.md
View file

@ -123,31 +123,38 @@ If Bun was just installed in Prerequisites (macOS/Linux), use `~/.bun/bin/bun` i
The CLI loads infrastructure config (database, tokens) from `~/.archon/.env` only. This prevents conflicts with project `.env` files that may contain different database URLs.
**IMPORTANT**: We'll now open an interactive setup wizard in a new terminal window. This allows you to enter API keys and tokens securely without exposing them to me (the AI assistant).
Credential configuration runs in a separate terminal so your API keys stay private — the AI assistant won't see them.
### 5a: Launch the Setup Wizard
### 4a: Launch the Setup Wizard
Run this command to open the setup wizard in a new terminal:
Run this command to attempt opening the wizard in a new terminal:
```bash
archon setup --spawn
```
**CRITICAL**: Do NOT run `archon setup` directly via Bash — it requires interactive input that I cannot provide. The `--spawn` flag opens a new terminal window where the user can interact directly.
**CRITICAL**: Do NOT run `archon setup` directly via Bash — it requires interactive input that I cannot provide. The `--spawn` flag attempts to open a new terminal window where the user can interact directly.
Tell the user:
> "I'm opening the Archon setup wizard in a new terminal window. In that window, you'll:
> 1. Choose your database (SQLite default or PostgreSQL)
> 2. Configure AI assistant(s) (Claude and/or Codex)
> 3. Set up any platforms you selected (GitHub, Telegram, Slack, Discord)
> 4. Enter API keys and tokens securely
> "Time to configure your credentials. This runs in a separate terminal so your keys stay private — I won't see them.
>
> The wizard will save configuration to both `~/.archon/.env` and the repo `.env`.
> The wizard will walk you through:
> 1. Database selection (SQLite default or PostgreSQL)
> 2. AI assistant configuration (Claude and/or Codex)
> 3. Platform tokens for any integrations you selected
>
> **Tell me when you've completed the setup wizard** so I can verify the configuration."
> It saves configuration to both `~/.archon/.env` and the repo `.env`."
### 5b: Wait for User Confirmation
**If the terminal opened automatically**, add:
> "Complete the wizard in the new terminal window that just opened."
**If the output says to run it manually** (common on VPS, WSL, SSH, Docker), add:
> "Open a separate terminal or SSH session and run the command shown in the output. Come back here and let me know when you finish so I can continue with validation."
Both paths are normal — the manual path is not an error.
### 4b: Wait for User Confirmation
Wait for the user to confirm they've completed the setup wizard before proceeding.

9
packages/cli/src/commands/setup.ts
View file

@ -1351,9 +1351,14 @@ export async function setupCommand(options: SetupOptions): Promise<void> {
if (result.success) {
console.log('Setup wizard opened. Complete the setup in the new terminal window.');
} else {
console.error(`Failed to open terminal: ${result.error}`);
console.log('');
console.log('Please run `archon setup` directly in your terminal.');
console.log('Next step: run the setup wizard in a separate terminal.');
console.log('');
console.log(` cd ${options.repoPath} && archon setup`);
console.log('');
console.log(
'Come back here and let me know when you finish so I can verify your configuration.'
);
}
return;
}