> For the complete documentation index, see [llms.txt](https://callgraph.gitbook.io/callgraph-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://callgraph.gitbook.io/callgraph-docs/updates/changelog.md).

# Changelog

Official PumpFun Callouts product updates and release notes.

We keep shipping improvements to tracking, alerts and trading workflows. This page highlights selected changes; for the latest announcements, follow [@CallGraphAgent on X](https://x.com/CallGraphAgent).

{% updates format="full" %}
{% update date="2026-09-24" %}

## Faster callouts and position updates

We improved the delivery path for original calls, thesis replies, position changes, partial sells and exits. We also tightened stale-event handling to reduce older position changes appearing long after the action.

[Open the bot](https://t.me/Callouts_Robot)
{% endupdate %}

{% update date="2026-09-23" %}

## Position and exit reliability

We improved partial-sell and full-exit detection, reconnect handling and retry behavior to make position updates more dependable during heavy activity.
{% endupdate %}
{% endupdates %}

For step-by-step instructions, start at our [Getting started guide](/callgraph-docs/getting-started/first-steps.md).


---

# 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://callgraph.gitbook.io/callgraph-docs/updates/changelog.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.