[FEATURE] CronCreate: option to suppress inline tool output (silent mode)

Resolved 💬 4 comments Opened Mar 19, 2026 by pdonorio Closed Apr 18, 2026

Description

When using CronCreate for recurring background monitoring, all tool calls and their results render inline in the chat conversation, interrupting the user's workflow. There's no way to run a cron tick "silently" — where tools execute but output doesn't appear in the conversation.

Use case

Periodic monitoring: a cron runs every X minutes, queries for example metrics and a database, then writes a one-line status to a file. The statusline command reads that file and displays it in the bottom bar. The user gets live monitoring without leaving Claude Code.

The problem: every cron tick shows 3-4 tool call blocks inline (MCP queries + file write), pushing the user's actual conversation out of view.

Expected behavior

A silent: true parameter on CronCreate that:

  • Executes all tools normally (MCP calls, file writes, etc.)
  • Does NOT render tool calls or results in the conversation
  • Optionally: only breaks silence if an error occurs or a condition is met (e.g. the prompt outputs text)
CronCreate({
  cron: "*/10 * * * *",
  prompt: "Query metrics, write to status file",
  silent: true  // <-- new option
})

Actual behavior

Every cron tick renders all tool calls inline, identical to user-initiated actions. There is no way to suppress this. Including "SILENT, do NOT output anything to the chat" in the prompt has no effect on tool call rendering.

Workaround

  • Write results to a file states/<name>-status.txt
  • Configure statusline to read the file
  • Increase cron interval to reduce noise (e.g. 10 min instead of 3 min)
  • Accept the inline clutter

Related issues

  • #32978 — Scheduled tasks: auto-archive sessions with no actionable output
  • #32806 — Feature: Persistent cron jobs via background daemon

Environment

  • Claude Code version: 2.1.79
  • OS: macOS 15.5 (Darwin 25.3.0)

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗