25 lines
1.7 KiB
Markdown
25 lines
1.7 KiB
Markdown
# skz-sloptrap
|
|
|
|
This workspace is the source code of `sloptrap`, eg. your own runtime.
|
|
Your author, 'sk4nz', has ran the command `sloptrap path/to/skz-sloptrap` and you are living in your own reflection.
|
|
|
|
# Keep Memory
|
|
|
|
Future sloptrap instances should add short, useful, durable notes they learn during their session to this file.
|
|
|
|
Only add high-signal information that is likely to help later runs.
|
|
Keep additions brief.
|
|
Do not remove existing instructions unless they are outdated or wrong.
|
|
|
|
---
|
|
# Session Memory
|
|
|
|
- When runtime changes need a fresh sloptrap session to validate, ask sk4nz to restart you and give an exact prompt to continue from the current checkpoint.
|
|
- Useful checks in the skz-sloptrap repo:
|
|
`shellcheck sloptrap`
|
|
`bash tests/run_tests.sh` (you can also run them separately)
|
|
- When running tests from inside sloptrap, inherited `CODEX_HOME=/codex` plus `SLOPTRAP_PREFER_CODEX_HOME=1` can leak into host-style child launches; ignore that preference when `HOME` has been redirected elsewhere and the runtime hints still point into the inherited `/codex` tree.
|
|
- Capability-enabled runs are Podman-only. `packet-capture` uses a dedicated helper container/pod, and host-network capture must prompt for an explicit acknowledgement on every runtime launch.
|
|
- `agent=opencode` should download the latest Linux CLI release artifact from GitHub into the build context and verify its digest; it should not depend on a host-installed `opencode` binary.
|
|
- For isolated networking, sloptrap exposes the host inside the container as `sloptrap.host`; opencode localhost URLs should be rewritten to that alias, and Podman `slirp4netns` runs need `allow_host_loopback=true` for host-local servers.
|