Repository navigation
Releases
v0.2.0 - Email-first workflow instructions
Email-first human input
Send the complete reviewed steps and an ordinary official login/action link in the email. There is no blanket requirement to return to GPT for every interaction.
- Optional canonical
action: bounded numbered steps, ordinary reply prompt, and completion hint - Explicit email-only action opt-in:
AAN_INCLUDE_ACTION=1or--include-actionin the producer - Configured
AAN_SMTP_REPLY_TO, exact transmitted Message-ID, request reference and current revision aan replies ingest --file message.emlandaan replies listfor a durable unverified-input review inbox- Current-request checks, replay/conflict protection, bounded MIME parsing, and obsolete-note handling
- Additive SQLite v1 → v2 migration, preserving existing event identities, pending requests, and queued deliveries
- Explicit database paths work without a home-directory profile
Important limits
Reply import is local and explicit. This release does not poll a mailbox, authenticate an email author, create an agent-answer channel, or configure SMTP/provider access. Imported replies always remain pending_unverified with can_authorize: false; they cannot approve, execute, resolve, or resume actions. A separately authorized host must establish owner intent and apply its original confirmation policy. Required platform confirmation forms still use their required surface. Passwords and sign-in credentials stay on the official service.
Defaults remain generic. Review action content before opting in: heuristic redaction cannot guarantee removal of private information. SMTP acceptance does not prove inbox delivery or human attention. No live SMTP/inbox/desktop end-to-end delivery was established.
Upgrading
Back up your existing SQLite state using a consistent SQLite backup while producers/workers are stopped; do not copy only a live WAL-backed .db file. First use of 0.2.0 upgrades the database to schema v2. Version 0.1.0 cannot open that upgraded schema; downgrade requires your retained v1 backup. Nothing installs a background service or creates credentials.
Downloads
Python 3.10+ is required. The .pyz runs without third-party runtime dependencies or package installation. The wheel and source archive are alternatives. Verify downloads against SHA256SUMS.txt.
中文摘要
新版本可以将经审阅的完整操作步骤和官方登录/操作入口直接写进邮件,并提供普通问题的回复提示,不再要求每次都回到 GPT。需要在生产方明确启用邮件正文,并自行配置 SMTP 和回复邮箱。
本地 .eml 导入只生成“未经验证的待处理输入”,不会自动收邮件、确认身份、授权、执行或恢复任务。平台要求的确认表单仍须在指定界面完成;密码与登录凭据留在官方服务。升级会保留旧事件、请求和发送队列并迁移数据库,回退旧版本须使用提前保存的一致性备份。
Verification
158 unique stdlib tests pass locally. The exact final commit 80a5cd2f881c5e7a62e03cfcf9dac2bb5780266b passed all nine Linux/macOS/Windows × Python 3.10/3.12/3.14 CI jobs, including compilation and zipapp smoke. SMTP tests are mocked; webhook tests exercise real loopback HTTP. The zipapp, wheel, and source archive were checked byte-for-byte against committed Python source. CI evidence.
Agent Action Notifier 0.1.0
Agent Action Notifier 0.1.0
Durable, notification-only alerts when an agent needs human input, permission, or review.
Included
- CLI/stdin and authenticated loopback webhook integration
- SQLite pending-request state and transactional at-least-once outbox
- Deduplication, retry/backoff, crash-lease recovery and stale-report handling
- Certificate-verified SMTP; same-session Linux/macOS alerts and Windows notification-area balloons
- Date-checked Codex/Claude hooks plus an explicit host integration contract
- Generic-by-default content, opt-in redacted summaries, safe review links
- English/Chinese setup guides, MIT license, no third-party runtime dependencies
Downloads
agent-action-notifier.pyz: standalone Python zipappagent_action_notifier-0.1.0-py3-none-any.whl: offline-installable wheelagent-action-notifier-0.1.0-source-8cb5969.zip: exact reviewed source snapshotSHA256SUMS.txt: integrity hashes for those three files
Requires Python 3.10+. Run python agent-action-notifier.pyz demo for a harmless local example. Read the setup/integration/security guides before selecting real notification channels. SMTP settings must be supplied securely; desktop delivery requires a supported interactive local session.
Verification and boundaries
111 unique stdlib tests, compilation, standalone demo and offline wheel installation passed locally. The exact-commit CI run passed all nine Linux/macOS/Windows × Python 3.10/3.12/3.14 jobs. Release target: 8cb5969f9a20a90f4db84f19d6dd3a992630baa6.
SMTP and desktop/subprocess adapter tests are mocked; webhook tests use actual loopback HTTP. No real mailbox delivery, visible popup, PowerShell notification execution, or live vendor-agent integration was exercised. Transport acceptance is not an inbox/display/read receipt. Windows uses a finite notification-area balloon request, not a native WinRT toast.
This release does not install services, configure credentials, deploy a public endpoint, or automatically attach to ChatGPT. Notifications never authorize, answer or resume an agent action; original human approval and security enforcement remain in charge. Work requiring approval stays paused, while separately authorized independent work can be reported honestly.