GitHub Codespaces

A Codespace is disposable — when it is torn down, everything the agent did in it goes too. AIStor Memory gives the agent in that Codespace durable memory: one mount of a MinIO AIStor Memory Bucket that it both works in and remembers through, so the files it edits and the knowledge it accumulates survive teardown and the next Codespace re-mounts the same state. Everything persists to your AIStor — your storage, your keys.

The AIStor Memory devcontainer Feature is how that memory reaches the Codespace. It injects an install script and an env-var contract into any devcontainer.json-aware host, so the same Feature mounts the Memory Bucket in Codespaces, VS Code Dev Containers, JetBrains Gateway, CodeSandbox, and Daytona's devfile import — write the integration once and it runs on all of them.

Quick start

Set the Codespaces environment once:

gh secret set -f - --user --app codespaces <<'EOF'
AIMEM_BUCKET=my-project
AIMEM_ENDPOINT=https://aistor.example.com
AIMEM_ACCESS_KEY=...
AIMEM_SECRET_KEY=...
EOF

Then add the Feature to your project's .devcontainer/devcontainer.json:

{
  "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
  "features": {
    "ghcr.io/miniohq/aimem:1": {}
  },
  "postCreateCommand": "aimem-mount"
}

Open the Codespace. The Feature mounts AIStor Memory at /workspaces/aimem before your first terminal opens.

Options

How the Feature works

The install script:

1. Installs fuse3, the aimem binary, and a setuid-root aimem-fusermount helper into the Codespace image (the helper lets the non-root remoteUser complete the mount).
2. Writes /usr/local/bin/aimem-mount, a wrapper that idempotently mounts the configured Memory Bucket. The wrapper reads AIMEM_BUCKET, AIMEM_ENDPOINT (or AIMEM_ENDPOINT_URL), AIMEM_ACCESS_KEY, and AIMEM_SECRET_KEY at runtime, and bails if the bucket, endpoint, or either credential is missing. It then launches the long-lived aimem process in the background (nohup aimem <bucket> <mountpoint> --endpoint-url … --local … --agent … --foreground &), so the process stays attached to its FUSE session for the container's life. Before returning, the wrapper waits until the mount is ready: it polls mountpoint for up to ~30s and fails if the mount never comes up. Re-running it is a no-op if the path is already mounted. The non-secret mount settings come from the Feature options as flags; credentials stay in the environment, never on the command line.
3. Drops /etc/profile.d/99-aimem-mount.sh so the mount happens on first interactive shell (best-effort).

If your tooling needs the mount before any shell opens, keep the postCreateCommand: "aimem-mount" line in devcontainer.json.

Portability

Because the same Feature runs on every host that reads the devcontainer.json spec, it mounts AIStor Memory on all of them — not just Codespaces. The Daytona page and E2B page both refer back to this Feature for the install half of their integrations.

Reference

• features/aimem/ — the Feature source.
• devcontainer-feature.json spec.