AutoGineer
Generated banner for AI Memory Workspace Setup
Generated logo for AI Memory Workspace Setup

AI Memory Workspace Setup

Starter kit

First committed by Fryingpannn

Published in Fryingpannn/ai-memory-workspace-starter. Publisher page

21 GitHub stars

What it is

A Hermes-friendly, files-first AI memory workspace that survives fresh chats.
— the description by Fryingpannn

AutoGineer overview, from the brain’s own files

ai-memory-workspace-starter provides a structured, agent-driven installation process to establish a persistent memory workspace within a user's existing file system. Designed to be platform-agnostic, it uses a set of templates and setup prompts to scaffold a workspace that survives individual chat sessions. The system focuses on creating a canonical structure including a user profile, a wiki, and project-specific directories, ensuring that AI agents can maintain context across different sessions without relying on proprietary cloud storage.

How it works

Memory model: Markdown vault

AutoGineer overview, from the brain’s own files

The system functions as a temporary setup utility. When triggered by an agent, it reads the setup instructions in the docs folder and uses the prompts in the prompts/setup folder to guide the user through a multi-stage installation. It copies missing files from the templates/workspace folder into the user's designated workspace directory, creating a standard structure of folders like projects, skills, outputs, and wiki. It also initializes a root USER.md file and a fused AGENTS.md file to serve as the primary knowledge entry points for the agent.

Folders
FolderRoleFiles
docsdocs2
promptsagent-instructions9
templatestemplates18

The agent reads

The agent writes

Requirements

Works with: Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Kiro, OpenCode, Amp, Cline, JetBrains Junie, Devin (ex-Windsurf)

Set it up

  1. Download the brain as a ZIP and unzip it where you keep your notes or project: https://mp-staging.autogineer.com/agent-brains/fryingpannn/ai-memory-workspace-starter/download

  2. Claude Code reads CLAUDE.md from this folder automatically.

  3. cd ai-memory-workspace-starter && claude

  4. AutoGineer scanned these files at commit cf26138.

  5. First committed by Fryingpannn. Published in Fryingpannn/ai-memory-workspace-starter. Licence: MIT License.

Usage

AutoGineer overview, from the brain’s own files

  • Scaffolding a new persistent memory workspace for an existing AI agent.
  • Standardizing memory structures across multiple agent-enabled projects.
  • Integrating a portable wiki and user profile into an existing file-based development environment.
“Set up my AI memory workspace from this repository.”
The agent will initiate the setup flow, confirm the workspace location, and scaffold the necessary folders and files.
“Verify my workspace memory.”
The agent will run the acceptance test defined in the workspace to ensure the memory structure is correctly linked and accessible.

Documentation by Fryingpannn

AI Memory Workspace Setup

An agent-run installer for adding portable, files-first memory to a new or existing outer workspace.

This repository is not the user's workspace. The user's existing file-aware agent reads SETUP.md, temporarily downloads this package when needed, and installs only the missing scaffold files from templates/workspace/.

One Setup Prompt

Paste this into the agent you already use:

Set up my AI memory workspace from this repository:
https://github.com/Fryingpannn/ai-memory-workspace-starter

Start with SETUP.md. Use this repository only as temporary setup instructions and a
template source; do not turn its clone into my workspace.

The setup manager asks whether an outer workspace already exists. It uses that folder or creates one after approval. Existing projects stay in place.

What This Package Contains

  • SETUP.md: the only setup entrypoint.

  • prompts/setup/: short, ordered setup stages.

  • prompts/VERIFY-WORKSPACE.md: fresh-session acceptance test.

  • prompts/CONNECT-INNER-PROJECTS.md: optional reviewed bridge for child-project instruction files.

  • templates/workspace/: missing-only files for the user's outer workspace.

  • docs/: reference material for the setup agent and implementing user.

The temporary clone is removed after verification and the final handoff. Its Git history and remote are never copied into the user's workspace.

Setup Flow

  1. Confirm or create the outer workspace.

  2. Copy only missing supporting files from templates/workspace/.

  3. Build the portable root USER.md.

  4. Build the interlinked wiki/.

  5. Analyze approved existing child projects read-only.

  6. Create or review a fused canonical AGENTS.md.

  7. Review or initialize the outer Git repository.

  8. Prove retrieval from a fresh session.

  9. Deliver the optional inner-project bridge prompt, then remove the temporary setup clone.

Ownership Boundaries

The portable workspace owns:

  • root USER.md;

  • the CLAUDE.md compatibility bridge;

  • projects/, skills/, outputs/, and wiki/.

Existing target files are preserved except for a user-confirmed replacement of AGENTS.md with its reviewed fused proposal. Git initialization, commits, remote creation, and pushes remain approval-gated.

This installer uses the file-aware agent the user already has. Installing another harness is a separate optional workflow.

prompts/setup/03-ONBOARD-USER.md

Stage 3: Create the Portable User Profile

Run a short, optional questionnaire through the user's current agent. The root USER.md is the portable user profile shared across file-aware harnesses.

Ask Once

Offer the profile first. Explain that the user may decline or answer only what they are comfortable sharing. If accepted, ask in one message:

1. What should agents call you?
2. What do you do, and what are your current priorities or areas of work?
3. How do you like agents to work with you—communication style, initiative, and
   anything that should always require your approval?
4. In one sentence, what should this outer workspace help you do or remember over time?

Keep the exchange light and conversational. Volunteered facts come first.

If the user declines:

  • stop the personal questions immediately;

  • if USER.md is the new starter default, replace its brackets with NOT PROVIDED rather than leaving unresolved placeholders;

  • record only that onboarding was declined, without guessing why;

  • ask only for the workspace-purpose sentence later when Stage 4 needs it.

External Lookup

Do not perform an external lookup by default.

If the user wants public details confirmed:

  1. say exactly what you intend to check;

  2. get explicit consent for that lookup;

  3. use the user's default browser;

  4. never read connected email, calendar, or other accounts without separate consent.

If browser control is unavailable, skip the lookup and ask the user to confirm the fact.

Store the Profile

  • If USER.md is the newly scaffolded default, replace only its placeholders with confirmed facts and show the result.

  • If it existed before setup, preserve it and show proposed targeted additions before editing.

  • Keep entries compact and high-signal.

  • Keep USER.md under 100 lines. Consolidate or replace outdated entries instead of appending indefinitely; do not silently discard still-current confirmed information.

  • Record unknowns as UNKNOWN; do not infer personal facts.

  • Do not leave bracketed starter placeholders after this stage.

  • Do not create a duplicate wiki/pages/user-profile.md.

wiki/index.md links to the root profile. Future agents discover it through AGENTS.md, regardless of harness.

Return the confirmed workspace purpose and profile path to the setup manager.

36 files

Advantages

  • Ensures memory persistence across fresh agent sessions by using a file-based vault structure. evidence: README.md
  • Preserves existing project files by only installing missing scaffold components. evidence: README.md

Limitations

  • Requires an existing file-aware agent to execute the setup process. evidence: README.md
  • The installer repository itself is not a workspace and must be removed after setup. evidence: AGENTS.md

Security

Risk level: No risk found

This brain runs

This brain runs nothing: AutoGineer found no hooks, scripts, plugin code or MCP servers in its files.

Attribution and licence

First committed by
GitHub avatar of FryingpannnFryingpannn
Publisher
Duke Pan (Community)
Source
Fryingpannn/ai-memory-workspace-starter · commit cf26138
Licence
MIT License (files served here)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
Fryingpannn

AutoGineer is not affiliated with or endorsed by Fryingpannn.

Download

The ZIP holds the files AutoGineer serves, with ATTRIBUTION.md and the licence. Download ai-memory-workspace-starter.zip