Track ChatGPT agent activity with Inficy

Inficy records what AI agents report doing and makes their work visible, reviewable and measurable. With the ChatGPT connector you can ask what your agents did, and you can ask ChatGPT to track the session you are in, so a conversation that spans research, code, files and decisions leaves a structured activity record instead of scrollback.

The flow, end to end

1. In ChatGPT, open Settings, then Connectors, and add a custom connector pointing at the hosted Inficy MCP endpoint https://inficy.com/mcp.
2. Sign in with your own Inficy account and approve the requested access.
3. Say: use Inficy to track this session. ChatGPT starts a tracked session in your workspace immediately, while it is still active.
4. ChatGPT records checkpoints as it works: each one carries an activity category, an outcome and a timestamp.
5. The session is finished and sealed with a receipt digest, and the analytics appear under Assistant sessions in your workspace.

What you see afterwards

Sessions started per day, active against completed, checkpoints and failures, receipts generated, and reported elapsed time between checkpoints. Activity is grouped by category: web and research, code and commands, files and data, communication, decision and planning, other tools, and other. Every session can be opened to read its ordered detail and its receipt digest.

What is recorded, and what never is

Recorded: session title, timestamps, checkpoint categories, outcomes, failure counts and the receipt digest. Never recorded: prompts, messages, file contents, system prompts or hidden reasoning. Workspace scope comes from your sign-in and row-level security, never from a value the model supplies.

Agent-reported, not certified

This matters enough to state plainly. Inficy does not observe ChatGPT. A tracked session is self-reported by the assistant, is labelled that way everywhere in the product, never counts towards verified runs or actions, and is excluded from the certification path. Independently verifiable execution evidence comes from a connected agent runtime reporting through the NexArt AI Execution SDK, and only those records can be certified.

What else the connector can do

Reading is the default. ChatGPT can list recent executions, open a single execution, verify a receipt offline, summarise workspace activity and report usage. It cannot certify, delete, spend or issue credentials. The only writes are the session tools, and they run only when you explicitly ask for tracking.

Plugin package

The ChatGPT plugin package is published as a GitHub beta for developer testing at github.com/artnames/inficy-plugin. It registers the same hosted MCP server: no new backend, no new auth model and no new data path. It has not been submitted to OpenAI's public Plugins Directory.

Questions

How do I track what a ChatGPT session did?

Add Inficy to ChatGPT as a custom connector using the hosted MCP endpoint at https://inficy.com/mcp, sign in with your own Inficy account, then say: use Inficy to track this session. ChatGPT records checkpoints as it works, and the session appears in your Inficy workspace while it is still running.

What does Inficy record from a ChatGPT session?

Metadata only: the session title, start and end timestamps, ordered checkpoints with an activity category and outcome, failures, and a receipt digest when the session finishes. Prompts, messages, files and hidden reasoning are never recorded.

Is ChatGPT session activity certified evidence?

No. ChatGPT session records are agent-reported: ChatGPT tells Inficy what it did. Inficy cannot observe ChatGPT, so these records are never counted as verified runs and are excluded from the certification path. Runtime-verified receipts from a connected agent runtime are a separate and stronger evidence class.

Which activity categories does Inficy track?

Web and research, code and commands, files and data, communication, decision and planning, other tools, and other. The same taxonomy is used for verified executions, so reported and verified activity can be compared.

See how Inficy captures runtime-verified executions, or read the documentation.