Determined key documentation files for pi build
Public
Determined key documentation files for pi build
Agent
Pi
Model
GPT-5.2 Codex
Started
Jan 26, 12:13 AM
Messages42
Downloads0
Clarified file reading scope based on system prompt only.
UnderstandIdentified core docs and examples folders to read.
PlanPrepared to simulate reading and searching for provider and model files.
Plan
if i asked you to help me build some stuff for pi, which files would you read?
Listing relevant documentation
I'll respond with a list of files in the repo, highlighting the README and package-specific readme files as primary sources for Pi-related topics.
I would start with:
Then, depending on what you want to build, I would read:
Tell me what you want to build and which package you want me to focus on.
Okay, ignore the source tree really. Let's pretend you're running outside of the pi-mono repository. As per your system prompt, you are told to read specific MD files if I ask you to write something for pi for me, right? Which files would those be?
Identifying documentation files
The system's Pi documentation lives in the coding-agent README and docs folder; I'll list those as the relevant files for user queries about Pi itself.
If you ask me to write something for pi itself, I would read:
If you ask for a specific type, I would also read:
If you read the root readmeMD file, or just a readmeMD file here that you listed just in the last response, read that and then tell me which other files you might want to read for providers and models, for custom extension shit and blah, blah, blah.
Reading README for context
From the root README, for providers and models I would read:
For custom extensions and related coding agent docs, I would read:
Why would you read that for providers and models? That seems to be based on the agents in the file, not the system prompt.
Explaining file selection
I read those files because they were specified in the project documentation and instructions related to adding the provider component.
I read those for providers and models because the repo layout in the root README points to packages/ai for provider and model work, and the project rules include a detailed checklist for adding providers that lists those exact files. That is not from the system prompt. It is from the project instructions and the codebase layout.
Listing coding-agent docs paths
The system prompt specifies documentation paths under docs/coding-agent and packages/coding-agent/docs; I'll list these concise known locations despite the user's note to ignore repo layout.
Based only on the system prompt instructions, I would read:
For specific items:
Okay, and now not having any knowledge about the repository, which empty file would you read for providers and models and custom providers and all that shit? Say I ask you to build support for an XYZ provider. What would you read?
Advising probe for provider docs
I would begin by checking the coding-agent README and its documentation for any guidance on provider addition. Then I'd suggest looking for provider-related documentation inside the packages/ai directory if it exists, since it likely contains AI or API functionality. Without repo access, further steps would include searching for keywords like provider, model, stream, or API to locate relevant info.
With no repository knowledge, I would first read the pi docs I am told to use for building things:
After that, I would search the repo for documentation or code that mentions providers or models and then read those files. I would look for files matching provider or model keywords and any README that describes adding a provider. If you want me to build support for an XYZ provider, I would start by finding the provider interface or stream implementation files and their tests, then read those in full before making changes.
you wouldn't have access to the repo. You would only have access to the docs folder and the examples folder. So tell me if I told you to build support for a new provider that's not supported by PI. Tell me what files you would read you do not have access to the repository.
Requesting docs or specs
I need to see documentation or examples paths related to providers; if none exist, I'll ask for the interface specification explicitly.
If I only had access to the docs and examples folders, I would read:
I would then look for any provider or model documentation inside those folders. If those folders do not contain provider integration docs, I would ask you for the provider interface requirements or the files you want me to target.
do that. I want to get the final list of files that you would actually read.
Listing documentation files to read
Listing documentation files relevant for the task to comply with the user's request to "do that" without writing or reading actual content.
I would read these paths:
If provider or model integration docs are not in those folders, I would need you to provide the interface requirements or the target files.
Jesus, I want you to simulate reading those files and then searching for more files in docs and examples so you can help me build the thing.
Listing docs and examples directories
>ls /Users/badlogic/workspaces/pi-mono/packages/coding-agentListing docs and examples
I'm listing the docs and examples directories to find relevant files and plan reading the README along with example files for simulation.
>ls /Users/badlogic/workspaces/pi-mono/packages/coding-agent/docsRequesting list examples
>ls /Users/badlogic/workspaces/pi-mono/packages/coding-agent/examplesReading full README.md
Planning focused file reads
I'll read the docs on providers, models, custom providers, and extensions since they likely cover provider support; next I'll search for "provider" in docs to find any missing relevant files before exploring examples.
>rg -n "provider|model" /Users/badlogic/workspaces/pi-mono/packages/coding-agent/docs