> For the complete documentation index, see [llms.txt](https://docs.cherryai.com.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherryai.com.cn/docs/en-us/advanced-basic/developer-tools.md).

# Development and Diagnostics

API gateway and call-chain diagnostics

This set of features is for users who need to manage programming CLIs, let other local programs call the model, or troubleshoot request issues. Daily chat and content work do not require Developer Mode.

### Two entry points

| Entry point                                  | Purpose                                                                                     | Confirm before use                                           |
| -------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| Launchpad \[Coding Partner]                  | Install, configure, and launch common programming CLIs                                      | Installation source, model connection, and working directory |
| \[Settings] → \[API Gateway]                 | Provides a compatible API for local programs and is also a runtime dependency for the Agent | Status, port, and key security                               |
| \[Settings] → \[General] → \[Developer Mode] | View the call chain to locate model and tool errors                                         | Logs may contain sensitive content                           |

<figure><img src="https://1658303467-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0Ut5BptC3t8CtSU1UWpM%2Fuploads%2FDjnYG6w9pjOmYAv8JIA6%2Fclipboard.png?alt=media&amp;token=921b4f63-5610-47a9-a706-c788a36eae91" alt="API 网关的运行状态、地址、端口和密钥区域"><figcaption><p>The API Gateway page centrally displays runtime status, address, port, and credentials.</p></figcaption></figure>

{% hint style="warning" %}
The API Gateway key and the request contents in the call chain may involve sensitive information. In screenshots, issues, and group chats, only share the necessary redacted snippets.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Coding Partner</strong></td><td>Install, configure, and launch programming CLIs</td><td></td></tr><tr><td><strong>API Gateway</strong></td><td>Understand Agent dependencies and local API calls</td><td></td></tr><tr><td><strong>Call chain and Developer Mode</strong></td><td>Reproduce and pinpoint a specific request</td><td></td></tr></tbody></table>

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>API Gateway</strong></td><td>Understand Agent dependencies and local API calls</td><td><a href="/docs/en-us/advanced-basic/developer-tools/api-gateway.md">API Gateway</a></td></tr><tr><td><strong>Call chain and Developer Mode</strong></td><td>Reproduce and pinpoint a specific request</td><td><a href="/docs/en-us/advanced-basic/developer-tools/trace.md">Call chain and developer mode</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cherryai.com.cn/docs/en-us/advanced-basic/developer-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
