container/bin not on PATH in interactive/manual sessions

Open
#196 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
dockerfile, shell
Domain
cli, devops, infrastructure

Research direction

Start by inspecting the Dockerfile, run-session.sh, and the shared shell startup files mentioned in the issue, then compare PATH in bot-spawned and manually started sessions. Confirm which startup paths are used by each session type. Done means tools in container/bin are available on PATH in both existing and newly started interactive sessions.

Written by the indexing model from the issue text.

Description

Problem

notify, push-view, gh-app-token, and other tools in container/bin/ are only on PATH in sessions spawned by the bot (lodge/telegram/slack). Interactive sessions started manually (e.g. claude code launched directly) don't source the session bootstrap that adds container/bin to PATH.

Current workaround

Added to ~/.bashrc and ~/.profile:

export PATH="/workspace/woltspace/container/bin:$PATH"

This fixes it for new shells. Existing sessions need export PATH="/workspace/woltspace/container/bin:$PATH" run manually.

Better fix

container/bin/ should be on PATH for all sessions — bot-spawned or not. Options:

  • Add it to the Dockerfile ENV PATH
  • Add it to a shared .profile or /etc/environment that all shells source
  • Add it to run-session.sh (already done for bot sessions, but not interactive ones)

Context

Found during uxwolt session 2026-03-19 while working on PR #193 (project viewer). notify command not found when called from an interactive Claude Code session.

Dominant language
Python
Stars
12
Forks
1
Avg merge
7h 13m
Merged PRs (30d)
31

Contributor guide

No contributing guide indexed for this repository

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 jerpint/woltspace

All issues in jerpint/woltspace

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.