bark-notify
Send Bark (day.app) push notifications after Codex completes a task. Use when one Codex or Claude run is finished, or when you need to notify on task completion with device name, project name, status, and summary.
Installation
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Voir la source ↗GuidesInstructions
Bark Notify
Overview
Send a Bark push notification after each Codex task. Use the helper script to resolve the project name and post to the Bark API.
User Preparation
1) Configure environment variables
You can add the following lines to ~/.bashrc (Linux) or ~/.zshrc (macOS) to set environment variables:
export CODEX_MACHINE_NAME="Machine-name" # e.g., Macbook
export CODEX_BARK_KEY="" # https://api.day.app/<CODEX_BARK_KEY>/
export CODEX_BARK_BASE_URL="https://api.day.app"
2) Add instruction in project AGENTS.md
For example, you can add this instruction to AGENTS.md:
Use skill bark-notify to notify users when each agent run is finished or when any notifications would be sent to users.
Workflow
1) Provide a project name source (optional)
- To override the folder name, define a project name in
AGENTS.mdusing one of:- YAML frontmatter:
project_name: My Project(orname:) - A plain line:
Project Name: My Projector项目名称:我的项目
- YAML frontmatter:
- If no name is found, the script uses the project folder name.
2) Send the notification at task completion
- Generate a short task title (3-8 words).
- Pick an execution status:
success,failed,partial,blocked, etc. - Write a brief result summary; avoid secrets.
Run:
python3 ~/.codex/skills/bark-notify/scripts/send_bark_notification.py \
--task-title \"...\" \
--status \"success\" \
--summary \"...\" \
--project-name \"...\"
Resources
-
scripts/send_bark_notification.py: Send the Bark notification and resolve the project name.
Exemples
Consultez les exemples du dépôt source.
Voir la source ↗Historique source
- Date d’indexation
- 2026-01-20
- Mise à jour de l’index
- 2026-01-28
- Branch
- main
Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!