Assemble and deliver one short morning digest for the person who owns the cron — what changed overnight in the sources they already connected, and what it means for their day.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The aim: one message, first thing, that answers "what changed since yesterday that I need to know about?" — so the owner starts the day without opening five tools. It replaces scanning, not thinking. If nothing changed, it says so and stops.
It runs as a scheduled cron turn owned by one person and delivers to their DM. It adds no
new tool: it reads the connectors that person has already connected and the memory of this
scope, uses memory for durable knowledge, files actions read / write for workspace files,
and the available command tool for scripts.
Use only what this deployment actually has, and say which sources you used. Check Connected apps and the keychain credentials in your prompt — those blocks are the complete allowlist. Typically: mail and calendar (what lands today, what's unanswered), the issue tracker (what moved, what's assigned to them), the repositories they work in (merged, failing, waiting on their review), and any shared credential vended for a news or search feed. Never advertise or invent a source that isn't listed.
ingest/ (e.g.
ingest/<source>.json, holding the last cursor and count) and pull only what is newer.
A checkpoint older than the source's retention window means a gap — say so rather than
implying continuity.memory tool, then advance the checkpoint. Memory is an index:
record the fact and its link, not the raw payload.ingest/delivered.json (the item
ids already sent) and drop anything the owner has seen unless it genuinely moved, in
which case lead with what changed. Append today's ids after delivering.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Act for an org admin — the admin API (scope directory, per-scope config & SOUL, any scope's memory, transcripts & captured prompts, files, user roster & external users, audit/errors/metrics/egress) accepts your token when the user you're talking to is an org admin and started this turn themselves. Use when an admin asks you to inspect or change anything org-wide or in another scope, or anyone asks whether they're an admin.
日本語の概要は準備中です。原文の説明を表示しています。
Drive a real stealth browser from your shell — act on websites (order food, file an expense, pull data behind a login), with per-person persistent sign-ins via the provider's managed auth (Kernel, Anchor, or Browserbase — picked by which API key you have). Use for ACTING on a site; to just read a page, use curl/wget first. Requires managed model access and a keychain grant for the browser provider key; follow the missing-key steps below.
日本語の概要は準備中です。原文の説明を表示しています。
Sign a cloud provider's CLI in (AWS, Google Cloud, Azure, or another) with a device-code flow, then run that CLI as the requesting user. Covers checking the CLI is installed, the login that survives the browser round-trip, and the boundaries on cloud writes.
日本語の概要は準備中です。原文の説明を表示しています。
Show the app connection picker or setup widget when users ask to connect apps, reopen setup, or need an app that isn't connected yet. Use QM’s authenticated backend for app discovery, consent, and execution without exposing project keys.
日本語の概要は準備中です。原文の説明を表示しています。
Connect an administrator-enabled SaaS app for a user with a one-time OAuth consent link.
日本語の概要は準備中です。原文の説明を表示しています。
Define a Loop — a durable scaffold that works a queue of recurring tasks autonomously (Sentry issues, Front tickets, small perf PRs) with its outputs held for human review. Use when someone wants an agent to keep doing a kind of work on a schedule, rather than one-off. Walks the interview, runs one real item live before arming anything, then writes the playbook and creates the loop.
日本語の概要は準備中です。原文の説明を表示しています。