SocialGPT 1.2.19 improves the workflow around “Verify fact”. A successful verification no longer has to be something you read once and then lose track of. The result can be saved as a fact card in Tools, reopened later, and shared when needed.
The update also makes troubleshooting clearer when a verification takes a long time or does not behave as expected.
Verifications are saved automatically
When a fact verification succeeds, it is saved as a fact card in the Tools account. This makes it possible to return to an earlier check without running the same search again.
It also becomes easier to review sources at your own pace, compare several verifications, and use an earlier result as a reference.
Saved fact cards can be shared
A saved fact card can receive a public share link. The same finished version can then be opened by somebody else without running the verification again.
This is useful when a result needs to be forwarded, used in a follow-up, or kept as supporting material for other documentation.
A more readable format
Fact cards are displayed in a more editorial format than before. Better Markdown support makes headings, lists, and links easier to read when a result is reopened or shared.
For the user, the result feels more like a finished text and less like raw internal output.
Discreet debugging when it is needed
The verification box now has a small dbg opener. It can show which phase the check is in, how long different parts take, timeout information, transport details, and a compact preview of the response or error.
The troubleshooting view stays out of the way until it is needed. It has its own scrolling area, and its content is easier to read and copy.
Timeout handling now also uses the same logic as other AI calls in the tool. A verification that becomes stuck should therefore no longer be able to keep counting indefinitely without ending clearly.
Clearer Facebook workflows
The Facebook-related admin and review workflows also provide a better overview. The panel more clearly shows queue and duplicate-checking status, the latest batch result, and when scrolling has reached content that is already known or previously sent.
This makes it easier to follow what the tool is actually doing without having to interpret internal details.