shell-pool / shell-pool/shpool
FR: add a --forward-env parameter to "shpool attach"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 67
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 15
Description
AI Policy Ack
Ack
What new feature do you want?
shpool attach --foward-env= (you could make it repeatable, or only once but with an array value or separator). So I can specify environment variables to forward.
Similar idea to --dir= option
I am writing a script which dynamically decides which environment variables to forward to a new session it creates.
Now, I can probably work around this by dynamically generating a config toml file, and passing it as --config-file. If I am confident the daemon is already running by now, it won't be forwarded to the daemon, it will just be used by the attach. Still, that's a pretty complex workaround for not having an option
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the shpool attach command handling and compare its existing --dir option with the configuration path used by --config-file. Determine how a repeatable or separated --forward-env value should reach a newly created session, then verify that selected environment variables are forwarded without requiring a generated configuration file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100