# session-manager

> Cross-project session management for OpenCode - access all sessions from all projects in one view

- Author: Claude Assistant
- Repository: mfethe1/skills
- Version: 20260123221508
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/mfethe1/skills
- Web: https://mule.run/skillshub/@@mfethe1/skills~session-manager:20260123221508

---

---
name: session-manager
description: Cross-project session management for OpenCode - access all sessions from all projects in one view
triggers:
  - sessions
  - cross-project
  - all-sessions
allowed-tools:
  - Read
  - Bash
---

# Cross-Project Session Manager

Access **all OpenCode sessions across all projects** from a single dashboard.

## The Problem

OpenCode stores sessions per-project. When you start the server from one directory, it only shows sessions from that project context. This means:
- Desktop sessions may not show on mobile
- CLI sessions from different projects are hidden
- You lose context when switching between projects

## Solutions

### 1. Session List CLI (All Projects)

```bash
# List ALL sessions across ALL projects
python skills/session-manager/scripts/all_sessions.py list

# List all projects
python skills/session-manager/scripts/all_sessions.py projects
```

### 2. Session Dashboard (Web)

```bash
# Start web dashboard on port 8888
python skills/session-manager/scripts/all_sessions.py dashboard

# Custom port
python skills/session-manager/scripts/all_sessions.py dashboard --port 9000
```

Then open http://localhost:8888 to see all sessions with clickable links.

### 3. Access E:\Projects from Web UI

The junction at `projects/` maps to `E:\Projects`:
- In web UI, browse to `projects/` to access E:\Projects
- Or type paths like `projects/jira_agent/src/` in file picker

## Session Storage Location

```
C:\Users\<user>\.local\share\opencode\storage\
├── project/              # Project metadata
│   ├── <hash>.json       # Project info (worktree path)
│   └── global.json       # Global project (no specific worktree)
├── session/              # Session data
│   ├── <project_hash>/   # Sessions for each project
│   │   └── *.json        # Individual session files
│   └── global/           # Global sessions
└── message/              # Message parts
```

## Access Sessions from Specific Projects

| Project | Sessions Location |
|---------|-------------------|
| E:\Projects\jira_agent | `session\54f4a36edc03c4b3be140b6d341fbd8c01fb4919\` |
| E:\Projects\geo | `session\8dd9603d7e9d6948299d76ea1d221d7c0d88f5ce\` |
| Global | `session\global\` |

## Known Limitations

- OpenCode currently scopes sessions to the current project
- Feature request for cross-project sessions: [GitHub #1877](https://github.com/anomalyco/opencode/issues/1877)
- Workaround: Use this skill's dashboard to access all sessions

## Verification

### Script Validation
Verify scripts work correctly before using:

1. **Syntax Check**
   ```bash
   python -m py_compile scripts/<script_name>.py
   ```

2. **Help Test**
   ```bash
   python scripts/<script_name>.py --help
   ```

3. **Dry Run** (if supported)
   ```bash
   python scripts/<script_name>.py --dry-run <test_args>
   ```

### Execution Verification
After running scripts:
- Check exit code (0 = success)
- Review stdout/stderr for errors
- Verify expected output files exist

### Failure Handling
If script execution fails:
1. Check error message for root cause
2. Verify input parameters are correct
3. Check dependencies are installed
4. Retry with verbose flag if available



## See Also

- [OpenCode Server API](https://opencode.ai/docs/server/) - REST API for session access
- [OpenCode CLI](https://opencode.ai/docs/cli/) - `opencode session list --all`