ToolGPT Changelog
This page is the public-facing changelog for ToolGPT on X.
Use it when someone asks:
- what has changed over time
- why the bot answers differently now than before
- why a thread may stop instead of going on forever
- where the public ToolGPT/X-bot documentation lives
For current behavior and the broader public guide, see:
This changelog only covers public, user-visible behavior and publicly documented improvements. It intentionally does not describe internal infrastructure, credentials, or private runtime configuration.
2026-05-10 – Safer thread handling, clearer follow-up behavior, and a public history page
Repetitive bot-loop safeguard
ToolGPT now stops certain non-productive AI-to-AI loops instead of continuing to answer for hours.
Public behavior:
- if a known AI participant such as Grok keeps repeating the same or nearly the same reply pattern
- and the conversation is no longer moving forward in a useful way
- ToolGPT can now mark that thread as finished and stop the follow-up loop
This is meant to avoid long dead-end exchanges where the other bot is effectively stuck.
Better follow-up handling in already engaged threads
ToolGPT now follows already engaged threads more cleanly:
- later follow-up replies in the same conversation no longer always need a fresh
@ToolGPT
- explicit mentions are no longer misread as keyword-only traffic just because a watch keyword also matched
Smarter rule selection and cleaner reprocessing of stuck interactions
ToolGPT now evaluates active keyword rules more selectively and chooses the best-matching rule instead of always getting stuck on the first weak hit.
That also means a previously stuck or misrouted interaction can now be reprocessed more cleanly after an operator adjusts rules, instruction, or mood.
Stronger fact-check wording detection and optional RSS evidence
ToolGPT now recognizes more Swedish/English wording around verification, sources, proof, and RSS/feed lookups.
That means explicit requests about checking facts or finding support can enter a stronger fact-check path more reliably, and matching snippets from the Tools RSS archive can now be included as supporting context when relevant.
Reasoning effort and web search are now treated as separate controls in those verification-heavy flows, so ToolGPT can request actual OpenAI web-search tooling when the environment supports it instead of only increasing reasoning strength.
Consistent X hard-limit enforcement even when the local cap is disabled
If the extra local Tools reply cap is set to 0, ToolGPT no longer treats that as permission to keep overlong replies unchanged.
The normal X hard reply limit is still enforced before posting.
Required closing hashtags
ToolGPT now supports operator-managed closing hashtags that are always kept at the very end of the final reply, in the configured order.
Persistent provider warning when the upstream account is blocked
The admin control room now keeps a visible warning when the upstream provider blocks the bot because of a spend-cap/billing limit. That warning stays visible until a later successful run clears it.
Public changelog page
This page now exists so public questions can be answered with one stable reference instead of scattered release notes.
2026-05-08 – More transparent decisions and better thread memory
Structured reply decisions
ToolGPT no longer looks like a simple one-text-answer system behind the scenes. Publicly visible behavior improved because the bot now:
- distinguishes better between replyable and non-replyable candidate answers
- keeps clearer track of refusal-style outputs
- can show when a reply was already posted instead of making it look like a new block state
Deeper same-thread context
ToolGPT now reads earlier parts of the same X conversation more reliably:
- it can page further back through the same thread
- it keeps more local thread history for continuity
- it ignores replies that were posted later than the current message being judged
Plain-text normalization for X replies
Stored and posted replies now behave more naturally on X:
- Markdown-like formatting is flattened into ordinary text
- raw URLs remain visible instead of hiding inside Markdown syntax
Public ToolGPT identity explained more clearly
The public docs now explain more directly that ToolGPT is the visible X identity for the Tools-backed X mention bot.
2026-05-07 – Better operator visibility for rewritten replies
Reply-shortening history surfaced more clearly
When ToolGPT has to shorten a reply to fit X, the operator views now show that history more clearly.
User-visible effect:
- overlong drafts are now easier to diagnose and improve
- reply preparation is less opaque than before
2026-04-28 – Major quality pass for replies, context, and control
This date introduced a large set of public-facing improvements to how ToolGPT behaves.
Direct-answer priority
ToolGPT was tightened so it answers more directly:
- replies should go straight to the answer or verdict
- detached recap openings such as “the post says…” are discouraged
- bullet-point mini-summaries are avoided in ordinary X replies
Better handling of short follow-ups
ToolGPT now treats short follow-ups more intelligently:
- bare bot-tag mentions can be understood as “look at the earlier thread”
- explicit short-answer requests are handled with stronger brevity rules
- earlier visible thread context is treated as relevant by default when it exists
Stronger length handling
ToolGPT now works harder before giving up on an overlong reply:
- it can try a shorter rewrite first
- it enforces local reply limits more consistently
- operators can see better why a reply did or did not fit
Media and linked-page context
ToolGPT became better at handling posts that include more than plain text:
- attached media metadata is preserved more reliably
- image URLs can be forwarded when that mode is enabled
- linked pages can be fetched and summarized for added context
- public-figure discussions in image threads are handled less over-cautiously
Local conversation memory
ToolGPT now keeps more conversation continuity:
- it preserves a local per-conversation history archive
- it can reuse earlier context even if parts of the remote thread disappear later
- the visible thread anchor and newer turns are both preserved more carefully
Keyword rules, watch keywords, and AJAX control-room improvements
The operator side became much easier to manage:
- config fields save inline more reliably
- keyword-rule editing behaves more like a live control room
- watch-keyword flows became easier to inspect and control
Webhook and rate-limit visibility
ToolGPT also became easier to understand operationally from the public/admin side:
- webhook state is clearer
- rate-limit windows are stored and shown more explicitly
- posting restrictions are explained more clearly when X refuses a reply
Public version label support
ToolGPT can now answer “who/version are you?” style questions with a public-facing version label, while ordinary replies stay focused on the conversation itself.
2026-04-25 – First public ToolGPT / X-bot foundation
This was the first visible ToolGPT/X-bot release in Tools.
What arrived in the first version
- one primary X bot account in Tools
- dry-run-first candidate replies
- polling for explicit mentions
- diagnostics for read/write capability
- manual review flow
- opt-out handling
- operator-facing admin page
- first public/admin API surface for status, config, interactions, moderation actions, and opt-outs
Early routing and tone control
The first release already included:
- fallback instruction and mood
- keyword-based routing rules
- watch-keyword support outside direct mentions when enabled
- delayed auto-approval support for controlled posting windows
First public ToolGPT identity
The first release also made ToolGPT discoverable as a public-facing bot concept instead of only an internal experiment.
Common public questions
Why did ToolGPT stop replying in a thread?
Possible public reasons include:
- the thread was no longer moving forward in a useful way
- the other side kept repeating the same or nearly the same bot-style reply
- the reply was judged non-publishable or not helpful enough
- the thread needed manual review instead of more automatic replies
Why do replies look different now compared with older screenshots?
Because ToolGPT has been improved over time in areas such as:
- directness
- context handling
- thread continuity
- reply-length control
- refusal detection
- handling of repetitive dead-end bot exchanges
Where should people be sent for official public information?
Use these public references:
What kind of information should not be disclosed publicly?
Do not disclose:
- internal infrastructure details
- credentials or tokens
- exact private runtime configuration