entireio / entireio/cli

Feature request: support Claude Code / Codex desktop and plugin sessions

Open
#1,697 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
5.1k
Forks
475
Avg merge
1d 11h
Merged PRs (30d)
178

Description

Problem or use case

Hi Entire team,

I would like to request support for capturing sessions from Claude Code and Codex when they are used through desktop apps or IDE/plugin environments, not only through command-line agent workflows.

Context

I enabled Entire in my repository and installed the agent integrations:

entire agent list
entire status
entire doctor

The local setup appears healthy:

Agents:
  ✓ claude-code
  ✓ codex

● Enabled · manual-commit · branch main
  Agents · Claude Code, Codex

✓ Metadata branches: OK
✓ Codex hook trust: OK
No stuck sessions found.

I also have checkpoints available:

entire checkpoint list

This shows checkpoints on the current branch.

However:

entire session list

returns:

No sessions.

From what I can tell, the current integration seems to depend on CLI-native hooks and transcript paths. That works for command-line agent sessions, but it does not seem to capture sessions created through desktop or plugin-based usage.

Request

It would be very helpful if Entire could support session tracking for:

  • Claude Code desktop / non-CLI usage
  • Codex desktop or IDE/plugin usage
  • Plugin-based environments where the agent is active, but not launched through the normal CLI lifecycle

Ideally, these sessions would appear in:

entire session list

and on the Entire web UI, with checkpoints linked to the corresponding session.

Why This Matters

A lot of actual agent work happens inside desktop apps or IDE plugins, not only inside terminal-launched CLI sessions. When those sessions are not captured, Entire can still show imported checkpoints, but the session timeline and resume workflow are missing.

This makes it harder to:

  • Review past agent work as a coherent session
  • Resume from a previous agent state
  • Connect checkpoints to the actual conversation/session that produced them
  • Use the web UI as the source of truth for all agent activity

Possible Approaches

Some possible solutions could be:

  • Provide official hooks or adapters for desktop/plugin environments
  • Support importing desktop/plugin transcripts into real Entire sessions
  • Allow manually attaching an imported checkpoint history to a session
  • Expose a lightweight local API that plugins can call for session-start, prompt-submit, tool-use, and stop
  • Clarify in the docs which Claude Code / Codex surfaces support full session tracking versus checkpoint-only import

Expected Behavior

After using Claude Code or Codex through a supported desktop/plugin environment, I would expect:

entire session list

to show the session, and for the Entire web UI to display the corresponding session/checkpoints.

Actual Behavior

Checkpoints can exist, but:

entire session list

returns no sessions, so the work does not appear as a resumable session.

Thanks!

Desired behavior

Proposed solution

No response

Alternatives or workarounds

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the mismatch with entire session list after checking entire checkpoint list, and compare it with the reported setup from entire agent list, entire status, and entire doctor. Read the existing CLI-native hooks and transcript paths for Claude Code and Codex, then define a supported desktop/plugin capture path. Done means supported sessions appear in entire session list and the web UI with linked checkpoints.

Written by the indexing model from the issue text.

Assessment

Domain
ai, cli, developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.