Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(opencode): close matching Engram session when OpenCode archive becomes idle

Closed
  • Is something wrong?
#1,263 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
backend

Research direction

Start from the OpenCode plugin integration (look for the archive handling entry point and the existing session-sync code it calls), then find how Engram sessions are transitioned to idle elsewhere so you can reuse that path on archive. Check umbrella issue #1192 and the related #1259 for the expected lifecycle semantics and where the mirrored plugin copies live. Done means: archiving an OpenCode session immediately closes the matching Engram session, all mirrored copies are updated, and focused tests plus docs cover the new behavior.

Written by the indexing model from the issue text.

Description

priority:medium status:needs-review type:feature
🔍 Problem Description

Archiving an OpenCode session should promptly transition its matching Engram session to idle. Without a dedicated archive-to-idle closure path, the Engram session can remain active until later synchronization, leaving session lifecycle state stale for users and downstream tooling.

💡 Proposed Solution

Add an OpenCode archive-to-idle session-closure feature that identifies the matching Engram session and closes it when the OpenCode session is archived. Keep the required mirrored plugin copies aligned, and cover the behavior with focused tests and documentation. This work may require a maintainer-approved size:exception because the mirrored plugin copies, tests, and documentation are all required for a complete change.

📦 Affected Area

Other

🔄 Alternatives Considered

Continue relying on delayed synchronization to close sessions. This leaves lifecycle state stale after an archive and does not provide the expected immediate archive-to-idle behavior.

📎 Additional Context

Part of umbrella issue #1192. This is intentionally scoped separately from #1259: it covers the explicit OpenCode archive-to-idle integration, including required mirrored plugin copies, tests, and documentation.

Dominant language
Go
Stars
7.1k
Forks
729
Avg merge
8h 35m
Merged PRs (30d)
319

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from Gentleman-Programming/engram

All issues in Gentleman-Programming/engram

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.