---
title: memhtml integrations shell
description: "Print an eval-able shell snippet that exports MEMHTML_ROOT and puts this binary's directory on PATH; --write appends it to your rc file inside a fence."
---

## 1. Synopsis

Print an eval-able shell snippet that exports MEMHTML\_ROOT and puts this binary's directory on PATH; `--write` appends it to your rc file inside a fence.

```sh
memhtml integrations shell [options]
```

## 2. Arguments

This command takes no positional arguments.

## 3. Flags

| Flag | Type | Default | Values | Description |
| --- | --- | --- | --- | --- |
| `--write` | flag | `false` | *no fixed set* | Append the snippet to the rc file inside `# MEMHTML:START` / `# MEMHTML:END` markers, replacing a prior fenced block. Without it the snippet is only reported. |
| `--rc` | string | *no default* | *no fixed set* | The rc file to write. Defaults to `~/.zshrc` when $SHELL ends in zsh, else `~/.bashrc`. |

Every command also accepts the [global flags](/reference/global-flags/).

## 4. Response

On success the command writes one JSON envelope to stdout, and its `type` is `integrations.shell`.

On failure it writes the failure envelope, whose `code` comes from [error codes](/reference/error-codes/).

[The JSON envelope](/reference/envelope/) gives the fields both shapes carry. [Response types](/reference/response-types/) lists every value `type` takes across the binary.

## 5. Further reading

No guide block names this command. The [guide](/reference/guide/) is the workflow prose the CLI ships beside the command table: which command to reach for, and in what order.

## 6. Provenance

A loader generates this page from `apps/cli/src/commands.ts` while the site builds, so no file in the repository holds it: the `COMMANDS` array there is the one source of argument parsing, of `memhtml manifest`, and of `AGENTS.md`. Change the registry and this page changes with it.