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
Copy file name to clipboardExpand all lines: AGENTS.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,6 @@
62
62
- Reproduce the issue with a focused test when feasible; if direct reproduction is impractical, document the exact reasoning and code evidence used to accept or reject the finding.
63
63
- Prefer adding or updating a regression test for every accepted review-bot bug before or alongside the fix.
64
64
- Do not patch purely to satisfy a bot comment if the behavior is correct, stale, already fixed, or the proposed change would make the implementation worse.
65
-
- After pushing any commit to an open PR, wait and poll for Qodo/review-bot comments and PR review status for about 30 seconds before reporting the push workflow as complete.
66
65
- After fixing an accepted review-bot finding, run the narrow regression test plus the relevant build/typecheck command, push the commit, and re-check the PR comments/status.
67
66
- In the completion report, distinguish confirmed fixes from stale or rejected bot comments.
68
67
@@ -142,6 +141,7 @@
142
141
- viewport(s)
143
142
- assertion/result summary
144
143
- screenshot absolute path(s)
144
+
- inline screenshot image(s) rendered in chat with Markdown image syntax using absolute local paths
145
145
- CJS command/result (when module-loading behavior was changed)
146
146
147
147
## Worktree Dev Server Rule
@@ -181,6 +181,7 @@
181
181
182
182
- When the user asks to test with Playwright, run the verification on the explicitly requested project/thread context (for example `TestChat`).
183
183
- Screenshot artifacts must show complete passing evidence for the tested feature, not only the base page load.
184
+
- Always show captured screenshots inline in the chat, not only as links or filesystem paths. Use Markdown image tags with absolute local paths, for example ``.
184
185
- For UI work, include dark-theme evidence in addition to the default/light-theme evidence unless the task is explicitly light-only.
185
186
- For refresh-persistence fixes, include a post-refresh screenshot that still shows the expected UI state.
Project-scoped automations are represented as Codex cron automations with a `cwds` array containing absolute project folder paths. The sidebar resolves display labels such as `TestChat` to the real cwd before saving so the Codex scheduler can run in the intended project. The project automation UI blocks unresolved/non-absolute project cwd values. Editing or deleting a project association on a multi-cwd cron automation preserves the other cwd associations and only deletes the automation folder when the final cwd is removed. Thread automations remain heartbeat automations keyed by `target_thread_id`.
6
+
7
+
Implementation facts:
8
+
-`src/server/codexAppServerBridge.ts` parses and serializes `cwds` in automation TOML records.
9
+
-`GET /codex-api/project-automations` returns project cron automations grouped by project cwd.
10
+
-`GET`, `PUT`, and `DELETE /codex-api/project-automation` read, save, and remove automations for one project cwd.
11
+
-`src/api/codexGateway.ts` exposes project automation helpers mirroring the thread automation helpers.
12
+
-`src/components/sidebar/SidebarThreadTree.vue` adds project menu `Add automation…` / `Manage automations…`, project row automation icons, and reuses the existing automation dialog with project-specific copy.
13
+
-`src/components/content/AutomationsPanel.vue` lists both thread heartbeat automations and project cron automations in one top-level panel. It sorts active automations before paused automations, newest first within each status group, and exposes row/detail edit buttons that open the shared automation editor.
14
+
- Project automations intentionally do not expose `Run now`; the existing manual run behavior remains thread-heartbeat-only.
Project automations extend the existing sidebar automation UI from thread-scoped heartbeat records to project-scoped cron records.
4
+
5
+
## Storage
6
+
7
+
Project automations use Codex cron automation TOML records with `cwds = ["<absolute project path>"]`. Sidebar display labels must be resolved to the real project folder before saving, so folder-name rows such as `TestChat` still write the scheduler-visible cwd. The UI/server reject unresolved non-absolute cwd values for project automation saves. Multi-cwd cron records keep their other cwd associations when edited or removed from one project, and the automation folder is deleted only when the final cwd association is removed. This matches Codex's project/folder automation shape while preserving thread heartbeat records that use `target_thread_id`.
The sidebar project row dots menu exposes `Add automation…` or `Manage automations…`. The dialog reuses the thread automation manager style, including multiple automation selection, schedule presets, status, and remove/save behavior.
14
+
15
+
Project rows show the same compact automation icon when at least one project automation is attached. The top-level Automations panel lists both project cron automations and thread heartbeat automations together, sorts active automations before paused automations with newest records first inside each status group, and exposes edit buttons that open the shared automation editor.
`Run now` remains available only for thread heartbeat automations because it queues a heartbeat message into a concrete thread. Project cron automations are scheduled against one or more working directories instead.
Copy file name to clipboardExpand all lines: llm-wiki/wiki/index.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,13 +14,15 @@
14
14
-[concepts/realtime-chat-rendering.md](./concepts/realtime-chat-rendering.md): realtime chat rendering, sync-churn reduction, and inline media sanitization.
-[concepts/thread-heartbeat-automations.md](./concepts/thread-heartbeat-automations.md): thread-scoped heartbeat automation storage, multi-automation management, and manual run behavior.
17
+
-[concepts/project-cron-automations.md](./concepts/project-cron-automations.md): project-scoped cron automation storage and sidebar management UI.
17
18
18
19
## Sources
19
20
-[../raw/features/integrated-terminal.md](../raw/features/integrated-terminal.md): source facts for the integrated terminal implementation and follow-up tests.
20
21
-[../raw/features/directory-hub-composio-skills-search.md](../raw/features/directory-hub-composio-skills-search.md): source facts for Directory Hub, Composio connectors, Skills search/install, and edge-case tests.
21
22
-[../raw/features/realtime-chat-rendering-inline-media.md](../raw/features/realtime-chat-rendering-inline-media.md): source facts for realtime chat rendering and inline media sanitization.
22
23
-[../raw/features/skills-route-ui-and-first-launch-card.md](../raw/features/skills-route-ui-and-first-launch-card.md): source facts for the Skills route rename, first-launch Plugins card, dark-theme fix, and dev-server workflow adjustment.
23
24
-[../raw/features/thread-heartbeat-automations.md](../raw/features/thread-heartbeat-automations.md): source facts for thread heartbeat automations, multiple automations per thread, and Run now queue behavior.
25
+
-[../raw/features/project-cron-automations.md](../raw/features/project-cron-automations.md): source facts for project cron automations in the sidebar.
24
26
-[../raw/projects/codex-web-local.md](../raw/projects/codex-web-local.md): immutable source snapshot for project facts.
25
27
-[../raw/fixes/opencode-zen-big-pickle-codex-cli.md](../raw/fixes/opencode-zen-big-pickle-codex-cli.md): Big Pickle + Codex CLI fix details.
26
28
-[../raw/fixes/opencode-zen-reasoning-content-proxy.md](../raw/fixes/opencode-zen-reasoning-content-proxy.md): Codex Web Local Zen proxy reasoning_content round-trip fix and Docker verification.
0 commit comments