# evergences Growth Beta — installation guide
Version 0.4.0-channel-first.1 • macOS • 17 October 2026

## What you are installing

A guided workbook to turn a task you know well into a small, testable offer. Work through capability, economics, offer/proof, buyer fit, a bounded demand test and repeatable delivery. Optional tools prepare focused prospect searches, outreach drafts and proposed call times.

Reasoning runs in your own signed-in official Codex host, using your own OpenAI account. The plugin contains no model API key and calls no Evergences inference backend. Your host plan and usage limits still apply, as do charges for any external services you separately choose. This is a local plugin, not a standalone model service.

It does not send messages, book meetings, process payments, publish content or run background campaigns. Search, Gmail and calendar steps need tools already authorized in your host. Missing access holds the dependent step. Examples are fictional and establish no achieved revenue.

## Before you begin

Use a Mac with a current official Codex CLI, signed in to your own OpenAI account, and an existing complete Python 3.10+ runtime with SQLite and IANA timezone data. CLI 0.162.1 was tested. The package installs no software, creates no credentials and requires no Evergences API key. Managed workspace rules may restrict private plugins.

The CLI route below has passed an isolated, unsigned-in install/uninstall test. Both skills were discovered and the guide was called through the official headless host. All nine tools also ran from the installed cache with synthetic data. This proves packaging and local operation, not a signed-in second-customer model conversation. Desktop UI use is untested. This beta does not support web, iOS, Android, IDE extension, Windows or Linux use.

## 1. Verify and extract

Download `evergences-growth-beta-0.4.0-channel-first.1.zip` and its checksum if provided. Expected SHA-256:

`1a96b8d3b913791aca2a8651ef7f491b3f74ed3c0582a3124cdea6d79dd0c939`

In Terminal, from the folder containing your download:

```sh
shasum -a 256 evergences-growth-beta-0.4.0-channel-first.1.zip
```

Compare the complete digest above. If the separate checksum file is alongside the ZIP, you can instead run:

```sh
shasum -a 256 -c evergences-growth-beta-0.4.0-channel-first.1.zip.sha256
```

Extract the ZIP. Keep the whole `evergences-growth-beta-0.4.0-channel-first.1` folder, including its hidden `.agents` folder and `plugins` folder, in a stable location you control, such as Documents/Evergences. Do not copy someone else's workbook/data folder or replace another plugin's files.

## 2. Check the existing runtime

In Terminal, type `cd `, drag the extracted versioned folder into Terminal, then press Return. From that folder run:

```sh
/bin/sh plugins/evergences-growth-beta/scripts/start-server.sh --check
```

Expect `runtime.ok: true`. With no local-saving setup yet, `configured: false` is expected. This read-only check creates no settings directory. If a prerequisite is missing, stop and keep the diagnostic. Nothing is automatically installed. Contact sean@evergences.com; do not broaden disk access or invoke an installer to force the test. The launcher deliberately avoids Apple's `/usr/bin/python3` shim.

## 3. Install the local plugin

From that same extracted folder:

```sh
codex plugin marketplace add . --json
codex plugin add evergences-growth-beta@evergences-growth-direct-beta --json
codex plugin list --marketplace evergences-growth-direct-beta --json
```

Read the results and stop on failure. The list should show the beta installed and enabled. These commands change your own host's plugin configuration/cache. Keep the extracted folder for later reinstall or updates. The beta uses a separate identity and does not migrate earlier Growth data. Do not install beta.1: beta.2 corrects a host-parser command issue and a prompt-length issue.

## 4. Start a new session and choose saving

Start a **new Codex CLI session**, then enter:

> Use $evergences-growth-beta:setup. Check the runtime, show where local saving would go, and explain the choice before enabling it.

You may stay in conversation-only mode. Your host still handles chat history under its own settings; conversation-only means the plugin does not save local workbook files.

For local saving, explicitly approve it in that interaction. The default folder is:

`~/Library/Application Support/evergences-growth-beta`

The helper writes owner-only settings and opaque local IDs. It seeds no database or sample. The first saved workbook creates the SQLite database. Those IDs are local bindings, not OpenAI/Gmail identities. Local records are not encrypted by this application and are not cloud-synced. Keep backups under your own controls.

Exclude restricted client material, raw private conversations, credentials, tax records and personal financial data. Use aliases and minimized references you have permission to store. Permission to store is separate from permission to publish or send.

## 5. Try a first session

> Use $evergences-growth-beta:growth-workbook. First compare distribution channels for my product or service. Then use one exact dated buying signal to propose one supported outcome and a concrete next step. Keep everything as drafts. Label unknowns; do not invent evidence or results.

A useful first result is one offer draft, transparent economic assumptions, buyer/trigger hypotheses, a bounded demand test and the next owner decision. The ZIP contains a fully hypothetical Planning Studio walkthrough: assumed $900 earned revenue minus $420 variable cost gives $480 contribution before acquisition/fixed overhead. These are example estimates, not actual results or cash received.

For prospects, ask for a search plan first. A plan contains no live results. Actual source dates and citations, recipient identity, relationship permission and mailbox history must precede a usable outreach draft. Call proposals need an actual human reply, all selected owner calendars, fresh busy periods, both timezones and constraints. A proposed time is not a booked event. Supplied source reports remain unverified by the local server.

## Pause or uninstall

To pause new local saves while retaining existing readable records, from the extracted folder:

```sh
/bin/sh plugins/evergences-growth-beta/scripts/start-server.sh --setup --disable-persistence
/bin/sh plugins/evergences-growth-beta/scripts/start-server.sh --check
```

Confirm `persistence_enabled: false`. Resume only with current explicit consent through the setup skill. If the helper reports legacy environment configuration, it cannot pause that profile; preserve it and seek an exact, separately reviewed configuration change.

To uninstall:

```sh
codex plugin remove evergences-growth-beta@evergences-growth-direct-beta --json
codex plugin marketplace remove evergences-growth-direct-beta --json
```

Start a new session afterward. Uninstall retains the beta's saved data folder; review/export what you need before a separate deletion decision. It does not remove another Growth version. Updates and migrations are not automatic.

Support: sean@evergences.com. Send the version and a minimized diagnostic, never private workbooks or tokens.

Official packaging guidance: https://developers.openai.com/plugins/build/plugins
Official plugin guidance: https://learn.chatgpt.com/docs/plugins