Droid is Factory’s AI-powered development agent. Entire integrates with Droid via its hook-based settings system, automatically capturing sessions and checkpoints. The Droid integration is in preview and may contain bugs.Documentation Index
Fetch the complete documentation index at: https://docs.entire.io/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- Entire CLI installed
- Droid installed
- A Git repository with Entire enabled
Enable
entire agent add factoryai-droid installs hooks into .factory/settings.json automatically.
How it works
How it works
The hooks track the full session lifecycle:
- Session Start — fires when Droid launches, creating a new Entire session.
- Turn Tracking — each user prompt triggers tracking via
user-prompt-submithooks. - Subagent Tracking —
pre-tool-useandpost-tool-usehooks capture Task tool invocations for nested session support. - Session End — fires when Droid exits, finalizing the session.
- Transcript Capture — session transcript is read from Droid’s JSONL log files.
- Session Storage — data saved to the
entire/checkpoints/v1branch.
What gets captured
What gets captured
| Data | Description |
|---|---|
| Conversation | Full transcript of prompts and responses |
| File changes | All files modified during the session |
| Tool calls | Tool invocations with inputs and outputs |
| Token usage | Input, output, reasoning, and cache tokens |
| Timestamps | Session, message, and checkpoint timing |
Features
Features
Nested session support. When Droid spawns sub-agents via the Task tool, Entire captures these as nested sessions through Nested sessions preserve the full context of complex multi-agent workflows.Rewind during sessions. Use
pre-tool-use and post-tool-use hooks:entire checkpoint rewind to restore to a previous checkpoint during or after a Droid session. See the rewind command reference for full flag documentation.Resume previous sessions. Switch to a session’s branch with entire session resume <branch>. The CLI restores the session log if needed and prints droid --session-id <id>. See the resume command reference for full flag documentation.Explain commits. Inspect any commit or checkpoint with entire checkpoint explain. See the explain command reference for full flag documentation.Caveats and limitations
Caveats and limitations
- The integration is in preview and may have rough edges.
- Session detection relies on hook-based process detection.
- Transcript capture depends on Droid writing JSONL session logs.
Best practices
Best practices
Commit at logical points. Commit when you’ve made meaningful progress:Check status regularly. Monitor your session with
entire status.Example workflow
Example workflow
Troubleshooting
Session not detected
Session not detected
- Ensure you’re in an Entire-enabled repo:
entire status - Verify Droid is running from within the repository
- Check that hooks are installed in
.factory/settings.json - Check Git hooks are installed:
ls .git/hooks
No checkpoints created
No checkpoints created
- Checkpoints require file changes — ensure Droid is modifying files
- Check your settings in
.entire/settings.json - Verify the
.factory/settings.jsonhooks are present
Transcript not captured
Transcript not captured
- Ensure Droid’s session storage exists at
~/.factory/sessions/<repo>/ - Check that JSONL transcript files are being written
- Look for errors in the Entire hook output