You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fac643f
Browse filesBrowse the repository at this point in the historyBrowse files
Reference children docs by path in overview prompts instead of inlining
Parent/repo overview prompts embedded the entire module tree — every
module's components list — as indent-4 JSON plus the full markdown of every
child doc. On large repos (wazuh: ~2.2M chars) that exceeds codex's hard
per-turn input cap of 1,048,576 chars, so every overview call failed with
input_too_large, surfaced misleadingly as "LLM returned empty content".
- build_overview_structure now strips components lists recursively and sets
an absolute docs_path per child instead of inlining docs (None when the
doc is missing). Wazuh-scale prompts drop from ~2.2M to ~83K chars.
- REPO_OVERVIEW_PROMPT / MODULE_OVERVIEW_PROMPT instruct the agent to read
the referenced files itself (backend.complete runs with ToolGroup.READER,
so file reads are available). Placeholders are unchanged, keeping the MCP
prompt_server rendering path working.
- Pin coding-agent-wrapper to the fork branch carrying the matching codex
provider fixes (stdin prompts, resume sandbox flag, and surfacing CLI
failures that were silently returned as empty turns).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: codewiki/src/be/prompt_template.py
+6-2Lines changed: 6 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -98,11 +98,13 @@
98
98
- The end-to-end architecture of the repository visualized by mermaid diagrams
99
99
- The references to the core modules documentation
100
100
101
-
Provide `{repo_name}` repo structure and its core modules documentation:
101
+
Provide `{repo_name}` repo structure:
102
102
<REPO_STRUCTURE>
103
103
{repo_structure}
104
104
</REPO_STRUCTURE>
105
105
106
+
The core modules' documentation is NOT inlined above. Each top-level module carries a `docs_path` field with the absolute path to its documentation file — read those files with your file-reading tools before writing the overview (skip entries whose `docs_path` is null).
107
+
106
108
Please generate the overview of the `{repo_name}` repository in markdown format with the following structure:
107
109
<OVERVIEW>
108
110
overview_content
@@ -117,11 +119,13 @@
117
119
- The architecture of the module visualized by mermaid diagrams
118
120
- The references to the core components documentation
119
121
120
-
Provide repo structure and core components documentation of the `{module_name}` module:
122
+
Provide repo structure of the `{module_name}` module (marked with `is_target_for_overview_generation`):
121
123
<REPO_STRUCTURE>
122
124
{repo_structure}
123
125
</REPO_STRUCTURE>
124
126
127
+
The child modules' documentation is NOT inlined above. Each child of the target module carries a `docs_path` field with the absolute path to its documentation file — read those files with your file-reading tools before writing the overview (skip entries whose `docs_path` is null).
128
+
125
129
Please generate the overview of the `{module_name}` module in markdown format with the following structure:
0 commit comments