SyedFahad7 · Nov 12, 2026 · Nov 12, 2026
diff --git a/agents/capabilities.mdx b/agents/capabilities.mdx
@@ -1,7 +1,7 @@
 ---
 title: "What your agent can do with Graphify"
 sidebarTitle: "What your agent can do"
-description: "Every hosted Graphify MCP tool, grouped by the job it does, with a prompt to paste for each one, a quick lookup table, and what each tool can't do."
+description: "Hosted Graphify MCP tools, grouped by the job each one does, with a prompt to paste, a lookup table, and what each tool can't do."
 keywords: ["graphify mcp tools", "what can my agent do", "mcp capability list", "agent prompts", "hosted mcp tools"]
 surface: "cloud"
 icon: "map"
@@ -16,7 +16,7 @@ When your coding agent connects to [Graphify MCP](/platform/graphify-mcp), it ge
 | You want to | Ask your agent to use |
 | --- | --- |
 | See which repositories it can query | `list_repositories` |
-| Find where something is defined | `graphify_find`, `search`, then `fetch` |
+| Find where something is defined | `graphify_find`. `search` and `fetch` are the pair the ChatGPT connector uses. Other clients can call them too. |
 | Find the files that matter for a question | `graphify_rank_files` |
 | Understand how a feature works | `query_graph`, `graphify_node` |
 | See who calls a function | `graphify_callers` |
@@ -29,13 +29,12 @@ When your coding agent connects to [Graphify MCP](/platform/graphify-mcp), it ge
 | Read how a pull request review went | `review_status` |
 | Switch between Graphify workspaces | `list_workspaces`, `set_workspace` |
 | Look up setup, which tool to use, or this workspace's plan limits | `graphify_help` |
-| Run a task handed off from a repository page | `run_repository_starter_task` |
 
 ## Find code
 
 <PromptBlock text="Use Graphify to find where invoice totals are calculated. Call graphify_find with short name fragments like 'invoice' and 'total', then graphify_rank_files with the question. Show the definitions with file paths." />
 
-`graphify_find` matches symbol names, so use a fragment, not a question. `graphify_rank_files` takes a plain-language question and returns files, not code. `search` and `fetch` work as a pair: `search` returns results with ids, and `fetch` reads the code behind one id.
+`graphify_find` matches symbol names, so use a fragment, not a question. `graphify_rank_files` takes a plain-language question and returns files, not code. `search` and `fetch` are the pair the ChatGPT connector uses. Other clients can call them too. `search` returns results with ids, and `fetch` reads the code behind one id.
 
 ## Understand how something works
 
@@ -85,10 +84,6 @@ See [Connect Google Drive](/platform/connectors#connect-google-drive).
 
 Most tools take a `repository_id`, either an id or a name like `acme/web-app`. `graph_stats` shows whether a repository is indexed and how large the graph is: node and edge counts, and languages. `set_workspace` switches the workspace for the current session. `graphify_help` answers questions about Graphify itself. `topic` is `setup`, `plan`, `repositories`, `tools`, or `troubleshooting`. `plan` is this workspace's plan and usage.
 
-## Run a handed-off task
-
-`run_repository_starter_task` runs a task handed off from a repository page. Pass its `task_id` unchanged. It returns source context for that task and records that the context was delivered. It does not record that your agent finished the answer.
-
 ## What the tools don't do
 
 - They don't edit your code or run your tests. Your agent does that with its own tools.

diff --git a/agents/overview.mdx b/agents/overview.mdx
@@ -32,7 +32,7 @@ The hosted server sends instructions on connect that map question types to tools
 | Which repositories or workspaces can I query? | `list_repositories`, `list_workspaces` |
 | How does X work? | `query_graph` |
 | Where is X defined? | `graphify_find`, or `graphify_node` for the body and its neighbors |
-| Find a definition by part of its name, then read it | `search`, then `fetch` with a result's `id` |
+| Find a definition by part of its name, then read it | `search`, then `fetch` with a result's `id`. The ChatGPT connector uses this pair. Other clients can call it too. |
 | Who calls X? | `graphify_callers` |
 | What is directly connected to X, including what it calls? | `graphify_impact` |
 | How does A reach B? | `graphify_trace` |
@@ -44,7 +44,6 @@ The hosted server sends instructions on connect that map question types to tools
 | What did the team decide about X? | `recall`. Pass `paths` and `symbols` for the code you are about to change so those notes can rank first. |
 | How do I set Graphify up, or which tool fits? | `graphify_help` |
 | What did a pull request review find? | `review_status` |
-| Run the task handed off from a repository page | `run_repository_starter_task`, with its `task_id` unchanged |
 
 Rules for the results:
 
@@ -64,7 +63,6 @@ The tools don't edit source files. Ask the user before you call a tool that chan
 
 - `remember` saves a note to the workspace's shared [Memory](/platform/memory). Save only what the user asked you to save. Saving records intake, not publication, until someone keeps it.
 - `set_workspace` changes which workspace, and so which repositories, the session reads. With `make_default`, it also changes the user's default. See [Graphify MCP](/platform/graphify-mcp#workspaces-and-mcp-sessions).
-- `run_repository_starter_task` runs a task handed off from a repository page and records that it delivered source context. Call it only for that task, and pass `task_id` unchanged.
 
 The hosted server does not capture tool calls as memory. `recall` reads notes the workspace already has, such as ones saved with `remember`, created through the API, or recorded from a workspace event such as a merged pull request.
 

diff --git a/concepts/ask-about-your-code.mdx b/concepts/ask-about-your-code.mdx
@@ -49,7 +49,7 @@ Your agent picks the tools. Your client shows the current set from `tools/list`.
 | `graphify_rank_files` | The source files most relevant to the question, not their bodies. |
 | `graphify_find` | Symbols whose name contains a fragment. |
 | `graphify_node` | One symbol's definition and its immediate neighbors. |
-| `search`, then `fetch` | `search` matches a name fragment and returns ids. `fetch` reads one result. Pass the `id` unchanged. |
+| `search`, then `fetch` | The pair the ChatGPT connector uses. Other clients can call them too. `search` matches a name fragment and returns ids. `fetch` reads one result. Pass the `id` unchanged. |
 
 A common pattern is to rank files or search by name, then read the definitions with `query_graph`, `graphify_node`, or `fetch`. The full list is in [Tools](/integrations/chatgpt#3-tools).
 

diff --git a/integrations/chatgpt.mdx b/integrations/chatgpt.mdx
@@ -59,7 +59,7 @@ Results come from the repositories indexed in your workspace. Open the source an
 
 ## 3. Tools
 
-Your client builds this list from the server's `tools/list` response. That response is the current set.
+Your client builds this list from the server's `tools/list` response. That response is the current set. `search` and `fetch` are the pair the ChatGPT connector uses. Other clients can call them too.
 
 | Tool | What it does |
 | --- | --- |
@@ -81,7 +81,6 @@ Your client builds this list from the server's `tools/list` response. That respo
 | `recall` | What the workspace remembers for a question. `paths` and `symbols` can rank notes about the code you are about to edit. |
 | `remember` | Save one durable note. Saving records intake until someone keeps it in **Memory**. |
 | `review_status` | Status and findings of Graphify's review of a pull request. Does not start a review. |
-| `run_repository_starter_task` | Run a task handed off from a repository page. Pass its `task_id` unchanged. |
 | `search` | Definitions whose labels match a name fragment. Pass a result `id` to `fetch`. |
 | `set_workspace` | Point this session at a workspace by its handle. `make_default` also replaces the default across sessions. |
 

diff --git a/llms.txt b/llms.txt
@@ -188,7 +188,7 @@ Use these first when you are an AI agent reading or acting on these docs.
 - [How AI agents connect, query and refresh](https://docs.graphify.com/agents/overview.md): For coding agents: how to connect to Graphify, which MCP tool answers which code question, how fresh the graph is, and what to do before sign-in.
 - [Headless agents and bots with hosted MCP](https://docs.graphify.com/agents/headless.md): Run Graphify from cloud agents, bots and CI: a person signs in once with OAuth, then the client refreshes tokens. What works today and what doesn't.
 - [Use Graphify from your agent: prompts that work](https://docs.graphify.com/agents/recipes.md): Copy-ready prompts for PR review, change impact, finding callers, tests for a symbol and onboarding, with the Graphify MCP tool each one triggers.
-- [What your agent can do with Graphify](https://docs.graphify.com/agents/capabilities.md): Every hosted Graphify MCP tool, grouped by the job it does, with a prompt to paste for each one, a quick lookup table, and what each tool can't do.
+- [What your agent can do with Graphify](https://docs.graphify.com/agents/capabilities.md): Hosted Graphify MCP tools, grouped by the job each one does, with a prompt to paste, a lookup table, and what each tool can't do.
 
 ## Cookbooks: Essentials