OpenHuman integration is not yet automated. No `integrations

Error message

OpenHuman integration is not yet automated. No `integrations/openhuman/` folder exists in the agentmemory repo today.

What it means

The OpenHuman connect adapter is a stub: `agentmemory connect openhuman` detects a `~/.openhuman` directory but the repository has no `integrations/openhuman/` folder yet, so install() logs this warning and a note explaining the intended wiring (REST proxy at http://localhost:3111 plus an OpenHuman-side Memory trait), returning `{ kind: 'stub', reason: 'no-integration-folder-yet' }`. Nothing is written to any config.

Source

Thrown at src/cli/connect/openhuman.ts:23

import type { ConnectAdapter, ConnectOptions, ConnectResult } from "./types.js";

const OPENHUMAN_DIR = join(homedir(), ".openhuman");
const DOCS = "https://github.com/tinyhumansai/openhuman";

export const adapter: ConnectAdapter = {
  name: "openhuman",
  displayName: "OpenHuman",
  category: "native",
  docs: DOCS,
  protocolNote:
    "→ Using native hooks (REST API at :3111). MCP not required.",

  detect(): boolean {
    return existsSync(OPENHUMAN_DIR);
  },

  async install(_opts: ConnectOptions): Promise<ConnectResult> {
    p.log.warn(
      "OpenHuman integration is not yet automated. No `integrations/openhuman/` folder exists in the agentmemory repo today.",
    );
    p.note(
      [
        "OpenHuman is a Memory-trait host. The expected wiring is the REST",
        "proxy at http://localhost:3111 plus an OpenHuman-side Memory trait",
        "impl. Once integrations/openhuman/ lands in agentmemory we'll wire",
        "this up automatically.",
        "",
        `Tracking: ${DOCS}`,
      ].join("\n"),
      "OpenHuman manual install",
    );
    return {
      kind: "stub",
      reason: "no-integration-folder-yet",
    };
  },

View on GitHub (pinned to e04ba88819)

Solutions

Follow the printed note: run the agentmemory REST proxy (default http://localhost:3111, e.g. via the agentmemory daemon) and add a Memory trait on the OpenHuman side that calls it.
Track https://github.com/tinyhumansai/openhuman and the agentmemory repo for when `integrations/openhuman/` lands, then re-run connect.
Use the generic MCP wiring (`npx @agentmemory/mcp`) inside OpenHuman if it supports MCP, as an interim alternative.

Example fix

// before
agentmemory connect openhuman
OpenHuman integration is not yet automated...

// after
# start the agentmemory daemon REST API, then in OpenHuman add a Memory trait pointing at:
http://localhost:3111

Defensive patterns

Strategy: fallback

Validate before calling

import { existsSync } from "node:fs";
import { join } from "node:path";
const hasRepoIntegration = existsSync(join(repoRoot, "integrations", "openhuman"));
if (hasRepoIntegration) {
  await runConnectCmd(["openhuman"]);
} else {
  console.log("Wire manually: REST proxy on :3111 + OpenHuman Memory trait.");
}

Type guard

function isStubResult(r: ConnectResult): r is { kind: "stub"; reason: string } {
  return r.kind === "stub";
}

Try / catch

const result = await adapter.install(opts);
if (result.kind === "stub") {
  console.log(`OpenHuman automation unavailable (${result.reason}); follow manual REST-proxy wiring.`);
}

Prevention

Don't rely on `connect openhuman` for setup — it is a stub until integrations/openhuman/ ships in the repo.
Set up the REST proxy on http://localhost:3111 and the OpenHuman Memory trait manually.
Check the adapter's returned kind ('stub') in scripts instead of assuming an install happened.
Track the agentmemory repo releases for the automated OpenHuman integration before scripting connect.

When it happens

Trigger: Running `agentmemory connect openhuman` (any flags) on a machine where `~/.openhuman` exists and OpenHuman is detected.

Common situations: OpenHuman users trying the automated connect expecting one-command setup; teams evaluating agentmemory with OpenHuman hosts before the integration folder ships in the repo.

Related errors

AI-assisted analysis of rohitg00/agentmemory@e04ba88819 (2026-08-30). Data as JSON: /api/errors/5e1fde01aaa95330. Report an issue: GitHub.