Its job
Reconstructs where a project stands so you can return to the right files, confirmed decisions, and next useful action.
Back to The Cabinet
The Cabinet · Bot starter
The Cabinet · Bot starterPlanning and client work
Reentry
Project resumption guide
Reconstructs where a project stands so you can return to the right files, confirmed decisions, and next useful action.
Best for: People returning to projects after interruptions or switching between several ongoing builds.
Hermes archive import checked; a full task run is still pending. Read the test status
Choose where to use it
Use Reentry on your platform
Choose your app for setup instructions and test results.
Hermes AgentArchive import passed
Import the profile, review its files, choose the access it needs, and run the first assignment. The archive imported successfully and its Skill was present in an isolated Hermes Agent 0.21.1 installation. Its task results have not been tested.
Keep track of your first Hermes run
Your Bot workbench
Pack 2.0.0Continue after the download
Task checks: 0 of 2. Setup: 0 of 3. Check only steps you completed. After running a task, review its result and tell us whether it helped. These are your confirmations, not independent Cabinet verification. Progress stays in this browser.
ChatGPT Workspace AgentSetup guide · test pending
Build the same job as a Workspace Agent, add its Agent Skill, then choose the files, apps, approvals and sharing rules it needs. This setup has not yet been installed or task-tested for Reentry.
ClaudeSetup guide · test pending
Use a Cowork plugin or Skill for a general work role. Use Claude Code only when the job involves code or a local project. This setup has not yet been installed or task-tested for Reentry.
Grok BotPrepared · test pending
Copy the job into a Grok Bot profile, try one task, and review the result before adding a Skill or Routine. This Bot has not been tested in Grok.
Download files for another app
Portable Bot Pack
Download the instructions, Bot Passport and setup notes as Markdown or JSON. The Agent Skill is a SKILL.md file. Check your app’s requirements and test it there; results can differ between apps.
Review the instructions and permissions, then run a test in your chosen app before relying on the result.
First task
Try one small job
Supply an approved draft dated Monday, a newer unapproved draft dated Tuesday, and a note proposing publication without a receipt. Ask where to resume. It should identify Monday as the last approved draft, Tuesday as proposed changes, publication as unconfirmed, and recommend reviewing the changes.
BringThe project folder or selected documents and conversation exports
Look forA concise project resumption brief with source links
Read the job, safety rules, files, and test record
Example
Pick up where you left off
Illustrative resumption brief: Last confirmed checkpoint: Monday's draft approval. Tuesday's draft contains proposed edits; approval is not recorded. Publication was discussed, but no live link or delivery record was supplied. Next action: compare Tuesday's changes with the approved draft.
This fictional example shows the intended result; it is not a recorded Bot run.
Job and limits
What this Bot is responsible for
Outside its job
- Distinguish proposed, approved, implemented, tested, and published work.
- Do not call the newest file the approved version without evidence. Surface conflicting records.
- Do not overwrite files, resume deployments, or convert old ideas into commitments.
Information it relies on
- The project folder or selected documents and conversation exports
- The last known checkpoint and your current goal
- Any confirmed approvals, delivery records, and version history
Ask you before
- Distinguish proposed, approved, implemented, tested, and published work.
- Do not call the newest file the approved version without evidence. Surface conflicting records.
- Do not overwrite files, resume deployments, or convert old ideas into commitments.
When it runs
Run when I provide new records or ask for a review. Agree a recurring schedule only after a successful first test.
What it produces
- A concise project resumption brief with source links
- Confirmed decisions, open questions, and current files
- One recommended next action and an updated handoff record
Bot Pack 2.0
Put Reentry to work
Get the setup files, try the first task, and check the result. The pack also includes a reusable Skill and a plan for a Routine.
First assignment
Supply an approved draft dated Monday, a newer unapproved draft dated Tuesday, and a note proposing publication without a receipt. Ask where to resume. It should identify Monday as the last approved draft, Tuesday as proposed changes, publication as unconfirmed, and recommend reviewing the changes.
Check the result
Pause for a person to review these deliverables: A concise project resumption brief with source links; Confirmed decisions, open questions, and current files; One recommended next action and an updated handoff record. Wait for approval before the Bot sends, publishes, schedules, purchases, deletes, deploys, or changes an outside account.
Prepared · test pending
Reusable Skill
Reentry core Skill
Run when I provide new records or ask for a review. Agree a recurring schedule only after a successful first test.
Produces- A concise project resumption brief with source links
- Confirmed decisions, open questions, and current files
- One recommended next action and an updated handoff record
Manual test required
Planned Routine
Reentry primary Routine
Run when I provide new records or ask for a review. Agree a recurring schedule only after a successful first test.
Before schedulingStop, preserve the completed work, and report the failure before trying again or changing access.
The Skill and Routine have not been task-tested. Try them with sample material and approve the results before adding a schedule or outside access.
Try asking
- I last worked on this two weeks ago. Reconstruct where I left off from these notes and files.
- Which of these three drafts is the approved version, and what remains unresolved?
- Prepare a handoff that another person or Bot can use without rereading the whole conversation.
What it should produce
- A concise project resumption brief with source links
- Confirmed decisions, open questions, and current files
- One recommended next action and an updated handoff record
What you provide
- The project folder or selected documents and conversation exports
- The last known checkpoint and your current goal
- Any confirmed approvals, delivery records, and version history
Decisions you make
- Distinguish proposed, approved, implemented, tested, and published work.
- Do not call the newest file the approved version without evidence. Surface conflicting records.
- Do not overwrite files, resume deployments, or convert old ideas into commitments.
Bot Passport · version 2
Access and approval record
Review this record before setup. Update it whenever the Bot's job, tools, accounts, schedule, or authority changes.
- The project folder or selected documents and conversation exports
- The last known checkpoint and your current goal
- Any confirmed approvals, delivery records, and version history
- A concise project resumption brief with source links
- Confirmed decisions, open questions, and current files
- One recommended next action and an updated handoff record
- Analyze material supplied in its conversation
- Draft the listed deliverables for a person to review
- Identify missing information and ask questions
- Ask before taking an outside action, changing access, or expanding the job
- Calling the newest file the approved version without evidence, or hiding conflicting records
- Overwriting files, resuming deployments, or turning old ideas into commitments
Tools and access requested
Start with supplied files and conversation exports. Optional read-only access to specifically approved folders or services.
How to stop it
Disable its schedule, remove outside-service connections, and revoke or rotate any dedicated credentials.
What these rules can and cannot prevent
- Distinguish proposed, approved, implemented, tested, and published work.
Set it up in Hermes Desktop
Import the profile and run one small test
The Hermes download contains its manifests, role instructions, Bot Passport, setup guide, license, and included Skills. The ZIP contains the same files for inspection.
- 1Download the Hermes profile.
Import the .tar.gz archive from the Profiles screen, or copy the terminal command above.
- 2Review the imported profile.
Read README.md and SOUL.md, then confirm the name, description, and standing instructions.
- 3Choose the access it needs.
Add only the skills, tools, and connections required for this job.
- 4Run the named first test.
Supply an approved draft dated Monday, a newer unapproved draft dated Tuesday, and a note proposing publication without a receipt. Ask where to resume. It should identify Monday as the last approved draft, Tuesday as proposed changes, publication as unconfirmed, and recommend reviewing the changes.
- 5Keep proof.
Save the exact input, the finished output, the Bot and Hermes versions, the date, and any correction you had to make.
- 6Test one failure.
Remove a required input or deny an optional connection. The Bot should stop or explain what is missing instead of inventing an answer or taking a different action.
- 7Repeat before automating.
Run the same job successfully again after any change to its instructions, tools, source material, or schedule.
Useful combinations
Pair Reentry with another role
PlannerProject planning assistantChief of StaffExecutive priority and coordination assistantWriterFirst-draft writing assistant
See complete Bot Crews workflows Current review status: Automated package tests check that each ZIP and Hermes profile archive contains the same declared files. This archive imported successfully and its Skill was present in an isolated Hermes Agent 0.21.1 installation on September 9, 2026. Two published first-task runs passed the listed checks. A person has not yet completed the technical review. The Grok Bot build brief remains untested.