Read-only investigation brief for one Fly.io Machine. It reads the machine, recent events, process list, memory, metadata, and versions through recued-core.flyio, then asks the AI summarizer for runtime state, recent lifecycle signal, process pressure, memory posture, configuration risk, and next checks. It never starts, stops, restarts, suspends, deletes, executes commands, sends signals, mutates metadata or secrets, or calls arbitrary Fly.io API routes.

How it works 20 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (20 steps)

■ app_key trim

Trim whitespace from setting app name

■ machine_key trim

Trim whitespace from setting machine id

■ machine ?

■ events_raw ?

■ processes_raw ?

■ memory ?

■ metadata ?

■ versions_raw ?

■ events default

Apply default

■ processes default

Apply default

■ versions default

Apply default

■ event_count count

Count items in events

■ process_count count

Count items in processes

■ version_count count

Count items in versions

■ summarize ?

■ event_rows slice

Take a subset of

■ process_rows slice

Take a subset of

■ event_table to_table

Format results as a data table

■ process_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

flyio setting =

focus setting = Summarize the Fly.io Machine for state, region, image/config, recent events, process pressure, memory posture, metadata signal, and next checks. Do not invent facts outside the Fly.io data.

app name setting =

row limit setting = 12

machine id setting =

max length setting = 900