How the team is picked

Step by step

From a folder to a list

Three parties take part. The labels between the steps show exactly what passes from one to another.

The app on your Macsees your files

Your Claudeon your Mac, your subscription

Argoforge serverruns no model

The app on your Mac1

You add a folder

The app gives the project a random number. The project's name and path stay in the app.

The app on your Mac2

The app counts files

It counts the files of each type and turns file, folder and dependency names into hashes. Build folders such as node_modules and hidden folders are skipped. A repository cloned into the project that you never committed to counts as a tool you use: it stays out of the count, and only its README goes to your Claude.

→ project number, counts, hashes

Argoforge server3

The server finds candidates

It recognises the stack from the hashes it knows, then searches its agent library and public catalogs of skills and MCP servers. MCP servers are searched only by the services your dependencies name (postgres, redis, aws, sentry, stripe and the like; a scoped package by its scope), never by frameworks; a project naming no service gets none. Each candidate gets a rating from 1 to 5. Agents and skills also move up or down a little by how useful they were to other users, and are checked for risky commands. MCP servers get no such check.

← candidates and a question for your Claude

→ excerpts of the project's documents · they never leave your Mac

Your Claude4

Your Claude describes the project

The app gives it the README and other project documents, up to about 16,000 characters. Your Claude writes 2–4 sentences on what the project is for, then names its main kinds of work (up to 4) and the services it uses.

→ the short description, kinds of work, service names

Argoforge server5

The server widens the search

If the description names work the files did not show, such as writing, marketing or a job search, the server adds agents and skills for it.

← the full list and a second question

Your Claude6

Your Claude chooses

It picks only from that list, and only what the project will really use, with a short reason for each. The limit grows with the project: up to 3 agents, 4 skills and 2 MCP servers per main kind of work, and no more than 12, 16 and 8 in total. Fewer is better: each one adds its description to every session. Other checked skills that fit are listed below, unticked, in case you want to add some.

→ the chosen names and reasons

Argoforge server7

The server puts the list together

It keeps your Claude's order and adds ratings and risk. It also writes the project's brief; the app fills in the name and path.

← the final list and the brief

The app on your Mac8

You look and decide

The app saves the brief in the project's hidden .argoforge folder, which git does not see. Installing is up to you: agents go to .claude/agents, skills are downloaded from GitHub at the exact checked version into .claude/skills, all named argoforge-…. MCP servers are not installed for you: the app shows a command to copy.

This is everything the scan in step 2 sends, for a real project:

{ "id": "dc964d04-0157-470b-9331-d64b4d50ced5",
  "facts": {
    "files": 56,
    "exts":  { ".md": 18, ".html": 14, ".js": 5, ".csv": 3, ".json": 2, ".css": 1, ".pdf": 1 },
    "names": [ "006b6735ed1532eb", "05bf5f6a58c903cc", "1050fe968f424511", … ],
    "deps":  [ ] } }

Your data

What stays on your Mac and what the server gets

Stays on your Mac

Your files and their contents
The project's name and folder path (the server gets them only inside the encrypted brief)
Documents your Claude reads to describe the project
The key that encrypts your pick's details, kept in the Keychain
The installed agent and skill files

Reaches the server

A random project number
File counts by type
File, folder and dependency names as hashes; the server can read back only common public names on its own list
The description, kinds of work and service names your Claude wrote; during the pick they are held in memory only, not written to disk
What was picked and what you installed; the brief, the reasons and the install commands are stored encrypted

The model

Where AI is used

Twice, in steps 4 and 6, and only on your Mac. The server never runs a model.

Your own Claude

The app runs the claude command already on your Mac, with your own subscription, on the model of the “Legion · pick” role (Opus by default; change it on the Hestia page's Models card). No extra key and no extra charge from us.

With nothing to act with

It runs in an empty temporary folder, with no tools, hooks, MCP servers or saved session. It can only read the text it is given and answer.

Two short answers

First a description of the project, then a choice from the list. The description goes into the brief, and each reason is shown next to its item. While the project's documents are unchanged, “Rebuild” reuses the last description instead of asking again; “Rebuild from scratch” asks anew.

Without Claude Code, or if it does not answer

If Claude Code is not installed, or does not answer within two minutes, the steps that need it are skipped. The server then describes the project from its file types and folder names and keeps only candidates for the kinds of work the files show. MCP servers stay only for services your dependencies name. The list is rougher, so install Claude Code for a better pick.

You decide

Nothing happens without you

Installed on your click

The list is only a suggestion. Agents and skills go into the project only when you press Install selected. Until then the pick writes only to the hidden .argoforge folder.

Every request is visible

The app's “What was sent” screen shows every request to the server, the pick's included, with its exact contents.

Removed exactly

Delete project first shows the exact list of what will go. Only what Argoforge added is deleted: its argoforge-… agents and skills, the .argoforge folder and the project's records on the server. Your own agents, skills and CLAUDE.md are never touched.

How the team for your project is picked