AI Memory Setup URL Builder

Build one exact, shareable setup URL and a tailored agent prompt before opening the full AI Memory Package Wizard. Choose the durable-memory shape and project behaviors, then copy either a Create prompt for inspected first-time setup or an Update prompt that preserves an established package.

Loops is on by default#

Project work should not quietly stop after one successful task. Loops is selected by default so the receiving agent completes the current reviewed cycle, considers what should be done next, names one bounded useful action, and provides a standalone suggested next prompt that the human can approve, edit, replace, or answer with keep going. Use loops=0 only when the package is deliberately one-shot.

Build the setup URL and prompt#

Create and Update use the same URL#

The prompt-intent choice is not a URL parameter. A Create prompt tells the receiving agent to inspect the codebase deeply, infer the actual stack, populate architecture and coding standards from repository evidence, create only required files, and merge any useful existing memory. An Update prompt assumes the package already contains deliberate structure and preferences, so it reads the current startup order first, preserves reviewed choices, and changes only stale, missing, conflicting, or weak records. Both prompts carry the identical generated Wizard URL.

What the URL controls#

• Long-term memory: active .uai/ always remains startup continuity; the selected docs, project wiki, LLMWikis.org, MemoryEndpoints.com MATM, or provider-neutral MATM target augments it.
• File Handoff: adds active Content and Improvement intake, disposition, proof-of-use, preservation, and completion records.
• Multi-Agent: adds portable identity, communication, acknowledgement, handoff, and evidence records.
• Advanced Persona: adds exactly 31 profile-required source records and five profile-required evidence records. All 30 personality records materialize; every source record requires resolvable source_excerpt_refs and a case-sensitive population_state set to reviewed_substantive, explicit_unknown, explicit_unknown_pending_source_review, explicit_not_disclosed, explicit_private, or reviewed_absent. The last five states require a substantive population_review_reason, and no aliases are accepted. Every one of the 36 canonical records requires one update_route containing the canonical persona route derived from the selected setup URL by removing only contract-declared receiver-export parameters. The complete selected URL remains package metadata. Persona safety-overlay export: explicitly adds disclosed non-empty receiver text after the unchanged persona; the receiver-only parameter and file remain outside the canonical bytes and digest. Create and Update prompts keep source persona, receiving-runtime constraints, observed variance, integration overlays, and public derivatives separate and require exact source-byte round-trip proof. A pending browser record is an inactive review scaffold; activation completion requires the shared validator with --readiness activation, zero pending records, complete reviewed source authority and integrity, no forced disclosure or inference, and exact blocker reporting when activation remains incomplete.
• Loops: defaults on and requires the next-action and suggested-next-prompt closeout. Turning it off writes loops=0 explicitly so a later agent does not mistake an omitted parameter for an instruction to stop looping.

Route-to-renderer coverage#

Update rule#

The generated URL is the package update URL. The wizard writes that exact URL into .uai/readme.human, AGENTS.md, and .uai/agent-pickup.uai so future humans and agents can return to the same setup without guessing.

Continue to the wizard#

After choosing the URL options, open the AI Memory Package Wizard to complete package metadata, credential inventory, source authority, receiver guidance, review, and export.