anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #9289] feat(tool): expose session context to child processes via environment variables #13056

New Issue
Open
opened 2026-02-16 18:17:56 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:17:56 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/9289

State: open
Merged: No

What does this PR do?

Exposes the current opencode session ID and title to child processes via environment variables, enabling user scripts and tools to correlate their work with specific opencode sessions.

Changes

  • OPENCODE_SESSION_ID: Unique session identifier (e.g., ses_xyz123)
  • OPENCODE_SESSION_TITLE: Human-readable session name (e.g., "Fix bug in auth flow")
    These are set dynamically in two user-facing command execution contexts:
  1. Bash tool (bash.ts)
  2. Prompt shell (prompt.ts)

Motivation

Users running iterative workflows (e.g., Ralph loops with multiple sessions per iteration) need to correlate logs and outputs with the specific opencode session they're running in. Previously, child processes had no access to session metadata.

Implementation Notes

  • Environment variables are set per-spawn (not globally) because sessions can change during interactive work
  • Session lookup includes graceful error handling to avoid breaking existing tests with mock session IDs
  • Both variables are always exposed; OPENCODE_SESSION_TITLE gracefully degrades if session lookup fails

How did you verify your code works?

  • Added a unit test for OPENCODE_SESSION_TITLE environment variable exposure
  • Used bun run dev with a prompt to echo $OPENCODE_SESSION_ID to verify variables are correctly passed to child processes
  • Didn't test on Windows

Example Usage

#!/bin/bash
echo "Session: $OPENCODE_SESSION_TITLE ($OPENCODE_SESSION_ID)" >> logs.txt

Closes #9292

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/9289 **State:** open **Merged:** No --- ## What does this PR do? Exposes the current opencode session ID and title to child processes via environment variables, enabling user scripts and tools to correlate their work with specific opencode sessions. ### Changes - **OPENCODE_SESSION_ID**: Unique session identifier (e.g., `ses_xyz123`) - **OPENCODE_SESSION_TITLE**: Human-readable session name (e.g., `"Fix bug in auth flow"`) These are set dynamically in two user-facing command execution contexts: 1. Bash tool (`bash.ts`) 2. Prompt shell (`prompt.ts`) ### Motivation Users running iterative workflows (e.g., Ralph loops with multiple sessions per iteration) need to correlate logs and outputs with the specific opencode session they're running in. Previously, child processes had no access to session metadata. ### Implementation Notes - Environment variables are set per-spawn (not globally) because sessions can change during interactive work - Session lookup includes graceful error handling to avoid breaking existing tests with mock session IDs - Both variables are always exposed; `OPENCODE_SESSION_TITLE` gracefully degrades if session lookup fails ## How did you verify your code works? - Added a unit test for `OPENCODE_SESSION_TITLE` environment variable exposure - Used `bun run dev` with a prompt to `echo $OPENCODE_SESSION_ID` to verify variables are correctly passed to child processes - Didn't test on Windows ### Example Usage ```bash #!/bin/bash echo "Session: $OPENCODE_SESSION_TITLE ($OPENCODE_SESSION_ID)" >> logs.txt ``` Closes #9292
yindo added the pull-request label 2026-02-16 18:17:56 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#13056
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?