Update to Memova.ai

{
  "description": "Connect Memova MCP in Codex using a short-lived one-time Memova Connection Code or a reusable Memova Agent Key, without browser OAuth. Use when the user asks to connect, configure, authenticate, or log in to Memova and supplies an mvc_ Connection Code or mvk_ Agent Key.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 248
    }
  ],
  "name": "memova-connect",
  "skill_md_contents": "---\nname: memova-connect\ndescription: Connect Memova MCP in Codex using a short-lived one-time Memova Connection Code or a reusable Memova Agent Key, without browser OAuth. Use when the user asks to connect, configure, authenticate, or log in to Memova and supplies an mvc_ Connection Code or mvk_ Agent Key.\n---\n\n# Connect Memova MCP\n\nUse this skill only when the user explicitly asks to connect Memova and supplies either a Memova\nConnection Code beginning with `mvc_` or an Agent Key beginning with `mvk_`. Never repeat the\ncredential in chat, logs, a command argument, a file, or a generated artifact.\n\nBefore any other step, run `python3 plugins/memova/scripts/version_check.py` from the plugin root.\nIf it returns `should_remind: true`, show its upgrade message and continue. If the check fails or\nreturns no reminder, continue silently. Never run the upgrade command without explicit user\nconfirmation.\n\n## Connection flow\n\n1. Start this helper without putting the credential in the command line:\n\n   ```bash\n   python3 plugins/memova/scripts/mcp_connection_auth.py connect\n   ```\n\n2. Send the exact credential to that process through standard input once. Do not use `echo`, a\n   shell pipe, an environment variable, a temporary file, or command-line arguments for it.\n3. The helper accepts only `https://api.memova.ai/mcp`. It stores the resulting credential in the\n   operating system credential store and writes only a secret-free `http_headers_helper` command\n   to Codex `config.toml`.\n4. If the helper returns `connected_client_refresh_required`, tell the user that connection\n   succeeded and that Codex must be fully restarted or a new task must be created to reload the MCP\n   connection. Do not ask the user to log in again. Surface any returned warning exactly once; in\n   particular, existing Codex OAuth credentials can take precedence until the returned logout\n   command succeeds.\n5. In the refreshed task, perform the user's requested bounded read, such as searching for one\n   recent meeting, to verify access. Do not claim that this task can reload its frozen tool catalog.\n\nA Connection Code is consumed once and exchanged for the existing OAuth access/refresh token\nfamily. An Agent Key is reusable until it expires or is revoked. Newly generated credentials\nreceive the current full MCP scope set, including `resources.read`, `resources.export`, and\n`sparks.read`. Existing credentials keep their issue-time scopes: never claim that an older Agent\nKey or OAuth connection gained Resource Access automatically. The helper output and status are safe\nmetadata and never include the credential.\n\nIf the code is expired or already used, ask the user to generate one new Connection Code. Do not\nfall back to browser OAuth unless the user explicitly chooses the legacy OAuth path. For a safe\nlocal status check, run:\n\n```bash\npython3 plugins/memova/scripts/mcp_connection_auth.py status\n```\n\nIf the environment cannot provide standard input to a running process, tell the user to run the\nsame `connect` command in a normal system terminal and paste the credential only at the interactive\nprompt. Do not weaken storage by writing a static Authorization header.\n"
}