redhat-developer / redhat-developer/rhdh-fullsend
Track upstream: sandbox_init_script field in harness schema
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 2
- Forks
- 7
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 8
Description
Upstream: Not yet filed on fullsend-ai/fullsend.
A sandbox_init_script field in the harness schema would allow pre-agent environment setup (sourcing env files, setting up toolchains, running diagnostics) without relying on `.env.d/` conventions or baking setup into skills.
Currently we work around this by mounting env files into `.env.d/` and relying on the sandbox startup loop to source them. A native init script would be more explicit and composable.
Impact: Would simplify sandbox bootstrap, especially for custom agents that need non-trivial setup before the agent starts.
TODO: File the upstream feature request on fullsend-ai/fullsend.
Migrated from `docs/known-issues.md`
Contributor guide
No contributing guide indexed for this repository
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
Review docs/known-issues.md and the current workaround described in this issue before filing the feature request on fullsend-ai/fullsend. Include the requested sandbox_init_script harness field, its pre-agent setup use cases, and the existing .env.d workaround; done means the upstream request is filed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100