@adaptiqai/mcp 0.1.1 → 0.1.5

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adaptiqai",
-  "version": "0.1.1",
+  "version": "0.1.5",
   "description": "AdaptiqAI's knowledge and memory tools in Claude Code: search, use and save your collections in the conversation you are in.",
   "author": {
     "name": "AdaptiqAI",

package/README.md

@@ -1,4 +1,4 @@
-# AdaptiqAI for Claude Code, Cline and any MCP app
+# AdaptiqAI for Claude Code, Cline, Codex and any MCP app
 
 Your AdaptiqAI knowledge and this conversation's memory, as tools for the
 agent: an MCP server, over stdio, on the AdaptiqAI core.
@@ -33,6 +33,33 @@ That writes `~/.cline/data/settings/cline_mcp_settings.json`:
 { "mcpServers": { "adaptiqai": { "transport": { "type": "stdio", "command": "npx", "args": ["-y", "@adaptiqai/mcp"] } } } }
 ```
 
+**Codex** (0.166)
+
+Connect to app in the AdaptiqAI console sets it up in the `adaptiq` profile it
+writes (`codex --profile adaptiq`). By hand, add it to the profile that runs
+Codex on AdaptiqAI, not to `config.toml`: Codex tells the server nothing of
+where its model requests go, and on another provider the tools would act on
+a conversation the model never reads.
+
+```toml
+[mcp_servers.adaptiqai]
+command = "npx"
+args = ["-y", "@adaptiqai/mcp"]
+env_vars = ["CODEX_HOME"]
+
+[mcp_servers.adaptiqai.tools.adaptiq_knowledge]
+approval_mode = "approve"
+
+[mcp_servers.adaptiqai.tools.adaptiq_memory]
+approval_mode = "approve"
+```
+
+Codex offers an MCP server's tools in a `namespace` tool of the Responses
+API (`mcp__adaptiqai`), and asks before each call of a tool that does not say
+it only reads, unless `approval_mode` says otherwise; saving knowledge still
+asks. Codex passes a server only a few variables of its environment, so
+`CODEX_HOME`, where it keeps its conversations, is named.
+
 **Any other MCP app**: run `npx -y @adaptiqai/mcp` as a stdio server.
 
 ## Sign in
@@ -45,6 +72,8 @@ comes first: knowledge has to be in the workspace the app's model reads.
   passes its environment on to the servers it starts, and the server uses the
   key Claude Code runs on when `ANTHROPIC_BASE_URL` is AdaptiqAI's. Cline's
   OpenRouter provider, pointed at AdaptiqAI, keeps its key in Cline's settings.
+  Codex hands a server no key of its own: Connect to app's profile starts the
+  server with the key Codex runs on as `ADAPTIQAI_API_KEY`.
 - **A key**: `ADAPTIQAI_API_KEY` in the server's environment.
 - **In the browser**: `npx -y @adaptiqai/mcp login`, or simply ask the agent
   for your knowledge: while the computer is signed out, the first tool call
@@ -58,12 +87,16 @@ alone.
 
 ## What it does
 
-- **`adaptiq_knowledge`**: what this conversation uses; search your saved
-  knowledge; use or stop a collection here.
+- **`adaptiq_knowledge`**: what this conversation uses; find words, ids or
+  names in the text of its collections, with the exact lines as
+  document:line; search your saved knowledge by name; use or stop a
+  collection here. An MCP server has no hook into a turn, so it can't tell a
+  turn which collections the conversation reads, as the other plugins do; the
+  tool and the server's instructions lead with find instead.
 - **`adaptiq_memory`**: how full the memory is; your saved collections; opens
   Knowledge in the browser to tidy up. It can't keep a conversation private,
-  as the DeepSeek Harness and Pi plugins can: Claude Code and Cline send their
-  model requests themselves, so AdaptiqAI saves what they send.
+  as the DeepSeek Harness and Pi plugins can: Claude Code, Cline and Codex
+  send their model requests themselves, so AdaptiqAI saves what they send.
 - **`adaptiq_create_knowledge`**: save material (text, files, links) as a
   collection, only when you ask for it. The server checks the request
   against your own messages in the conversation, as every AdaptiqAI plugin
@@ -77,15 +110,16 @@ Harness and Pi plugins have (`agentTools` in `@adaptiqai/core`).
 MCP has no conversation id, so the server reads each app where it keeps its
 own:
 
-| | Claude Code 2.1.308 | Cline 3.0.74 |
-|---|---|---|
-| What the app hands the server | `CLAUDE_CODE_SESSION_ID`, `CLAUDE_PROJECT_DIR` and its own environment; `_meta["claudecode/toolUseId"]` on every call | nothing (no id in the environment or `_meta`) |
-| What its model requests name | `x-claude-code-session-id`, the same id | body `session_id`, only on its OpenRouter provider |
-| How the server finds the call's conversation | the transcript (`~/.claude/projects/…/<id>.jsonl`) that holds the call's tool-use id: Claude Code keeps the server across `/clear` and `/resume`, so the starting id goes stale. An agent's call is in the agent's own transcript (`<id>/subagents/…/agent-<agent>.jsonl`), and is the session `<id>.<agent>`, as the gateway names an agent's requests; what an agent saves stays the chat's | the conversation whose messages file (`~/.cline/data/sessions/<id>/<id>.messages.json`) holds the call, not answered yet: Cline writes it there a few milliseconds before it makes it. Cline's hub runs every task in one process, so when two tasks make the same call at once, or no file holds it, the record started last before this server wins: Cline starts a server for each conversation |
-| What has to be true for it to reach the model | Claude Code on the AdaptiqAI gateway with `CLAUDE_CODE_GATEWAY_HINT_HEADERS=1` (the gateway names a chat only from `x-claude-code-request-class: main`) | Cline's OpenRouter provider with its base URL set to the AdaptiqAI gateway |
+| | Claude Code 2.1.308 | Cline 3.0.74 | Codex 0.166 |
+|---|---|---|---|
+| What the app hands the server | `CLAUDE_CODE_SESSION_ID`, `CLAUDE_PROJECT_DIR` and its own environment; `_meta["claudecode/toolUseId"]` on every call | nothing (no id in the environment or `_meta`) | `_meta.threadId` and `_meta.sessionId` on every call |
+| What its model requests name | `x-claude-code-session-id`, the same id | body `session_id`, only on its OpenRouter provider | body `client_metadata.thread_id`, the same thread |
+| How the server finds the call's conversation | the transcript (`~/.claude/projects/…/<id>.jsonl`) that holds the call's tool-use id: Claude Code keeps the server across `/clear` and `/resume`, so the starting id goes stale. An agent's call is in the agent's own transcript (`<id>/subagents/…/agent-<agent>.jsonl`), and is the session `<id>.<agent>`, as the gateway names an agent's requests; what an agent saves stays the chat's | the conversation whose messages file (`~/.cline/data/sessions/<id>/<id>.messages.json`) holds the call, not answered yet: Cline writes it there a few milliseconds before it makes it. Cline's hub runs every task in one process, so when two tasks make the same call at once, or no file holds it, the record started last before this server wins: Cline starts a server for each conversation | the thread `_meta.threadId` names: an agent the chat starts is a thread of its own, as its requests are; what an agent saves stays the chat's (`_meta.sessionId`). The chat's rollout (`$CODEX_HOME/sessions/<year>/<month>/<day>/rollout-<time>-<thread>.jsonl`, under the day the thread began) gives its folder and the person's messages |
+| What has to be true for it to reach the model | Claude Code on the AdaptiqAI gateway with `CLAUDE_CODE_GATEWAY_HINT_HEADERS=1` (the gateway names a chat only from `x-claude-code-request-class: main`) | Cline's OpenRouter provider with its base URL set to the AdaptiqAI gateway | Codex on the AdaptiqAI gateway with a key Connect to app made for Codex (the gateway names a thread only for one), and the server in that profile alone |
 
 When that is not so, every tool says why instead of attaching knowledge to a
-conversation the model never reads. An app other than these two names no
+conversation the model never reads; Codex alone gives the server no sign of
+it, so there it rests on the profile. An app other than these three names no
 conversation, so its tool calls are refused the same way.
 
 The transcript also holds your own messages, which `adaptiq_create_knowledge`