-
Notifications
You must be signed in to change notification settings - Fork 290
Factory Droid checkpoints show 'Unknown' agent in entire.io even though checkpoint metadata contains the correct agent/model #859
Description
What happened?
I am using Entire with Factory Droid plus an external checkpoint remote. The local CLI/session data looks correct, and the pushed checkpoint metadata also contains the correct agent and model, but the entire.io UI shows the agent label as Unknown instead of something like Factory AI Droid / Factory DROID CLI.
What I verified locally:
entire sessions listshowsFactory AI Droidentire sessions info b01c7e9b-7bab-46fa-8dae-42fa6c0ee01a --jsonreturns:agent: Factory AI Droidmodel: gpt-5.4---xhigh-(OpenAI-API)-4
- the pushed checkpoint metadata in the external checkpoint repo also contains the correct values
Remote checkpoint metadata example for checkpoint d5cbf8114ff0:
{
"checkpoint_id": "d5cbf8114ff0",
"session_id": "b01c7e9b-7bab-46fa-8dae-42fa6c0ee01a",
"agent": "Factory AI Droid",
"model": "gpt-5.4---xhigh-(OpenAI-API)-4"
}So the checkpoint data appears to be captured and pushed correctly, but the UI still renders the agent as Unknown.
Steps to reproduce
- Enable Entire for a repo with Factory Droid hooks installed
- Configure an external checkpoint remote, e.g.
entire enable --checkpoint-remote github:SvenMeyer/aertura-blockchain-frontend-entire - Work in the repo using Droid /
factoryai-droid - Commit changes so Entire writes a checkpoint trailer, e.g. commit
e530a7fwith checkpointd5cbf8114ff0 - Push normally so
entire/checkpoints/v1is synced - Open the linked session/checkpoint in entire.io
- Observe that the agent label is shown as
Unknown
Entire CLI version
0.5.3
OS and architecture
Linux 6.12.77-1-MANJARO x86_64 GNU/Linux
Agent
Factory Droid (preview) / factoryai-droid
Terminal
unknown
Logs / debug output
Relevant log lines show the CLI is detecting the Droid agent correctly:
{"level":"INFO","msg":"session-start","agent":"factoryai-droid","session_id":"b01c7e9b-7bab-46fa-8dae-42fa6c0ee01a","model":""}
{"level":"INFO","msg":"turn-end","agent":"factoryai-droid","session_id":"b01c7e9b-7bab-46fa-8dae-42fa6c0ee01a","model":"gpt-5.4---xhigh-(OpenAI-API)-4"}
{"level":"INFO","msg":"prepare-commit-msg: agent commit trailer added","checkpoint_id":"d5cbf8114ff0","session_id":"b01c7e9b-7bab-46fa-8dae-42fa6c0ee01a"}The checkpoint metadata pushed to the remote repo also contains the correct agent/model:
{
"agent": "Factory AI Droid",
"model": "gpt-5.4---xhigh-(OpenAI-API)-4"
}Additional context
- code remote:
git@github.com:SvenMeyer/aertura-blockchain-frontend.git - checkpoint remote:
git@github.com:SvenMeyer/aertura-blockchain-frontend-entire.git - checkpoint branch exists remotely and includes the expected metadata files
- docs used during investigation:
/cli/checkpoints/cli/external-agents/integrations/factory-droid
- this feels more like an ingestion/rendering issue on the Entire side than a local hook/config issue, because the remote checkpoint metadata already contains the correct agent name