Prepare State Hub retirement baseline
This commit is contained in:
parent
2217bdd9f5
commit
5927591be8
46 changed files with 32583 additions and 62 deletions
|
|
@ -19,6 +19,28 @@ cd ~/state-hub
|
|||
make bootstrap-env
|
||||
```
|
||||
|
||||
The bootstrap enables `sandbox_workspace_write.network_access` in the
|
||||
operator's Codex `config.toml`, removes any default `dev-hub` Codex MCP
|
||||
registration, then checks whether a Codex sandbox can reach
|
||||
`http://127.0.0.1:8000/state/health`. Use `--skip-codex` to omit this step, or
|
||||
run it independently:
|
||||
|
||||
```bash
|
||||
make configure-codex
|
||||
```
|
||||
|
||||
If verification still reports isolated networking, a managed Codex permission
|
||||
profile is overriding user configuration. Retry State Hub REST/CLI commands with
|
||||
escalated execution or change that managed profile; do not infer that the API is
|
||||
down until the same health check has been run outside the sandbox.
|
||||
|
||||
The slim six-tool Codex MCP server remains available for explicit testing, but
|
||||
is not recommended while the Codex MCP bridge adds substantial call latency:
|
||||
|
||||
```bash
|
||||
make configure-codex WITH_MCP=1
|
||||
```
|
||||
|
||||
On a clean Ubuntu 24.04 machine, allow package installation explicitly:
|
||||
|
||||
```bash
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue