feat(daily-briefing): add dynamic Notion task integration via agent tools#132
feat(daily-briefing): add dynamic Notion task integration via agent tools#132jayhaldors wants to merge 1 commit intoopenclaw:mainfrom
Conversation
|
Thanks for the pull request! This repository is read-only and is automatically synced from https://clawhub.ai, so we can’t accept changes here. Please make updates on the website instead. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 185a711d35
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| **Only if `config.notion.enabled` is true.** | ||
|
|
||
| If a `config.notion.tasksDatabaseId` is provided, use your `notion_query_database` tool to fetch tasks due today, or tasks categorized as "In Progress", "Doing", or "High Priority". |
There was a problem hiding this comment.
Step 6 checks config.notion.enabled and config.notion.tasksDatabaseId, but the gathered JSON schema used by this skill only exposes flat config fields (for example emails_enabled, emails_limit, etc. in scripts/daily_briefing_orchestrator.sh), and no config.notion object is emitted. Because the workflow requires the agent to rely on that gathered file, this condition will never become true in normal runs, so the new Notion integration is effectively always skipped.
Useful? React with 👍 / 👎.
| - If `config.notion.enabled` is true, use the top 1–2 items retrieved from Notion as the Daily Anchors and omit the dedicated Notion section, weaving them directly into the flow of the briefing. | ||
| - Otherwise, only include if you can **confidently infer 1–3 real priorities** from user-provided context. |
There was a problem hiding this comment.
This instruction mandates omitting the dedicated Notion section whenever Notion is enabled, which conflicts with the layout and section-format rules that explicitly include a Notion Focus for Today section when Notion tasks are found. That contradiction makes the output contract ambiguous and will lead to inconsistent briefings depending on which rule the model prioritizes.
Useful? React with 👍 / 👎.
1 participant
No description provided.