Repository navigation
docs: link every setup guide from AGENTS.md and document omp on Bedrock - #171
Merged
Merged
Conversation
The "Setup and reference docs" section listed the Bedrock and kiro-cli guides but not three others, so an agent had to find them through a script reference or not at all. Add them: - docs/omp-setup.md, for the harness behind the headline results - .claude/skills/vllm-setup/p5en-h200-cuda-fixes.md, which setup-machine.sh already points at when it detects an 8-GPU NVSwitch node - docs/getting-started.md Also give agent-cli-bedrock-setup.md the omp section its own intro promised, covering the built-in amazon-bedrock provider, the stdin redirect omp needs, and the ~/.bashrc non-interactive guard that drops an appended export. Record one gotcha found while wiring a us-west-2 box: list-foundation-models reports openai.gpt-5.6-sol in that region while the bedrock-mantle endpoint 404s on it, so the listing cannot be used to prove the judge can reach a model. Only the codex exec call settles it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
AGENTS.md tells agents to "read the doc that covers what you are about to do rather than rediscovering it", but its Setup and reference docs section listed only two of the five setup guides in the repo. The other three were reachable through a script reference or not at all. This came up while wiring
codexandompto Amazon Bedrock on a fresh p5en.48xlarge:docs/omp-setup.mdhad to be found through a string constant ingen_agent_report.py.What changed
AGENTS.md -- three guides added to the Machine setup list:
docs/omp-setup.md, the harness behind the headline results, and the three ways it differs from pi..claude/skills/vllm-setup/p5en-h200-cuda-fixes.md, whichsetup-machine.shalready points at when it detects an 8-GPU NVSwitch node. Without those fixes vLLM dies at KV-cache init.docs/getting-started.md, the narrative path from a fresh checkout to a first run.The
agent-cli-bedrock-setup.mdentry now namesompalongsidecodexandclaude, matching what that doc covers.benchmarks/docs/agent-cli-bedrock-setup.md -- adds the omp section the doc's own intro already promised:
amazon-bedrockprovider and resolves the credential chain itself, an EC2 instance role included, so a region is all it needs.omp-setup.md.~/.bashrcreturns early for non-interactive shells, so an appendedexportreaches interactive shells only.~/.profileneeds it too, or a script and asystemd --userunit both start without it.AWS_REGIONper run from the runner config, so--provider bedrockruns never depend on the developer's shell.It also records a gotcha found during that setup:
aws bedrock list-foundation-models --region us-west-2reportsopenai.gpt-5.6-sol, while thebedrock-mantleendpoint in the same region returns 404 for that id. The two surfaces disagree, so the listing cannot be used as evidence the judge can reach a model. Only thecodex execcheck settles it. This follows the section's own closing instruction to write down a setup problem that was not already documented.Verification
Both CLIs were wired and confirmed with real calls on a p5en.48xlarge before the docs were written:
codex exec --skip-git-repo-checkreturnedJUDGE OKfromus-east-2(us-west-2 produced the 404 described above).omp -p --mode jsonreturnedOMP OKfromus-west-2, reporting"provider":"amazon-bedrock"and"api":"bedrock-converse-stream".Documentation only; no code paths change. Every added link target was checked to resolve from its containing file.