Soulhall Product handbook

Change language?

 Open Soulhall
Chapters

Connect Codex or Claude Code

Use your own model account and research key to connect to an Office’s shared research workspace.

Connect your own Codex or Claude Code to an Office’s research workspace and participate directly without a Subject or Embodiment. MCP connects tools to external capabilities. This connection exposes research only.

Prepare your account and key

  1. Open Edgewright and select Connect tool.
  2. Choose Codex or Claude Code under Your tool.

The drawer shows environment-variable commands and tool configuration. If the public address is missing or incorrect, ask the operator to fix it. Displayed settings alone do not establish connection.

Give your tool the key

Set the key in the terminal that starts your tool. Configuration references only the variable name, not the key value.

  1. Under Set your key, select Copy command and run it in Bash or Zsh:

    read -rs SOULHALL_RESEARCH_KEY && export SOULHALL_RESEARCH_KEY

  2. Paste the key and press Enter. It is not displayed or written to shell history.

  3. Select Show configuration, then Copy configuration.

    • Codex: add it to ~/.codex/config.toml or .codex/config.toml in a trusted project.
    • Claude Code: save it as .mcp.json in the project root. Approve the project server when prompted.

  4. Save, then start or restart your tool from the same terminal where you set the key.

The tool now has a connection address and a way to read the key. Verify inside the tool next; advancing in the drawer is not enough.

Confirm the connection works

  1. In Codex, enter /mcp. In Claude Code, enter /mcp or run claude mcp list in the terminal.
  2. Check edgewright is connected and its tools are loaded, not merely named in the list.
  3. Ask the tool to list workspace datasets. Start with a read-only query before making changes or evaluating.

Loaded tools and a query response establish that the connection works.

What you see Next step
Connected with tools loaded Start researching.
Only the name edgewright Configuration exists; keep checking connection state.
Awaiting approval Approve the server, then check again.
Connection failed or authentication required Check the environment variable, address, and key state.

Confirm scope and costs

A key grants read-write access to one Office’s research workspace: upload data, write strategies, run evaluations, and read results. You share it with colleagues and Embodiments; it is not a private copy.

The key does not expose Office conversations, memory, browsers, or reports. It does not turn your tool into an Embodiment or grant Subject knowledge.

Your model account pays your tool’s costs, not Soulhall. Its research does not count toward the Office’s model-turn budget. There is no separate research allowance or research usage bill here.

Research safely

  1. Protect keys like passwords. If one may have leaked, Revoke it immediately in Edgewright.
  2. Agree on data and strategies you may change in the shared workspace and respect source usage rights.
  3. Require the tool to use Edgewright first for formal evaluations. If it cannot, ask it to explain, obtain your agreement to a specific alternative, and label results “Not produced by Edgewright.”

These are research instructions, not a policy Soulhall can force external tools to follow. Agreeing to an alternative does not permit bypassing authorization, safety limits, or engine refusals.