waypoint-codex 0.1.8 → 0.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -2,9 +2,17 @@
|
|
|
2
2
|
|
|
3
3
|
This repository uses Waypoint as its operating system for Codex.
|
|
4
4
|
|
|
5
|
+
If the repo needs custom AGENTS guidance, write it outside the managed `waypoint:start/end` block in `AGENTS.md`. Treat the managed block as Waypoint-owned and replaceable.
|
|
6
|
+
|
|
5
7
|
## Session start
|
|
6
8
|
|
|
7
|
-
|
|
9
|
+
Run the Waypoint bootstrap only:
|
|
10
|
+
|
|
11
|
+
- at the start of every new session
|
|
12
|
+
- immediately after a compaction
|
|
13
|
+
- when the user explicitly asks for a rerun
|
|
14
|
+
|
|
15
|
+
Bootstrap sequence:
|
|
8
16
|
|
|
9
17
|
1. Run `node .waypoint/scripts/prepare-context.mjs`
|
|
10
18
|
2. Read `.waypoint/SOUL.md`
|
|
@@ -15,6 +23,11 @@ At the start of every session:
|
|
|
15
23
|
|
|
16
24
|
Do not skip this sequence.
|
|
17
25
|
|
|
26
|
+
- Do not skip it at new-session start or after compaction.
|
|
27
|
+
- Do not rerun it mid-conversation just because a task becomes more substantial.
|
|
28
|
+
- Earlier chat context or partial memory from the current session does not count as a substitute when a new session starts or a compaction happens.
|
|
29
|
+
- If you are unsure whether a new session started or a compaction happened, rerun it instead of guessing.
|
|
30
|
+
|
|
18
31
|
## Repository memory model
|
|
19
32
|
|
|
20
33
|
The repository should contain the context the next agent needs.
|
|
@@ -3,7 +3,18 @@
|
|
|
3
3
|
|
|
4
4
|
This repository uses Waypoint as its Codex operating system.
|
|
5
5
|
|
|
6
|
-
|
|
6
|
+
Waypoint owns only the text inside these `waypoint:start/end` markers.
|
|
7
|
+
If you need repo-specific AGENTS instructions, write them outside this managed block.
|
|
8
|
+
Do not put durable repo guidance inside the managed block, because `waypoint init` may replace it during upgrades.
|
|
9
|
+
|
|
10
|
+
Stop here if the bootstrap has not been run yet.
|
|
11
|
+
|
|
12
|
+
Run the Waypoint bootstrap only in these cases:
|
|
13
|
+
- at the start of a new session
|
|
14
|
+
- immediately after a compaction
|
|
15
|
+
- if the user explicitly tells you to rerun it
|
|
16
|
+
|
|
17
|
+
Bootstrap sequence:
|
|
7
18
|
1. Run `node .waypoint/scripts/prepare-context.mjs`
|
|
8
19
|
2. Read `.waypoint/SOUL.md`
|
|
9
20
|
3. Read `.waypoint/agent-operating-manual.md`
|
|
@@ -11,7 +22,13 @@ Before doing substantial work:
|
|
|
11
22
|
5. Read `.waypoint/context/MANIFEST.md`
|
|
12
23
|
6. Read every file listed in the manifest
|
|
13
24
|
|
|
14
|
-
This is mandatory, not optional.
|
|
25
|
+
This is mandatory, not optional.
|
|
26
|
+
|
|
27
|
+
- Do not skip it at session start or after compaction.
|
|
28
|
+
- Do not rerun it mid-conversation just because a task is substantial.
|
|
29
|
+
- Earlier chat context or earlier work in the session does not replace the bootstrap when a new session starts or a compaction happens.
|
|
30
|
+
- If you are not sure whether a new session started or a compaction happened, rerun it.
|
|
31
|
+
- Do not skip the context refresh or skip files in the manifest.
|
|
15
32
|
|
|
16
33
|
Working rules:
|
|
17
34
|
- Keep `.waypoint/WORKSPACE.md` current as the live execution state
|