A
Aditya Parikh
Hi ClickUp team,
I’m using AI Agents heavily, including an automation‑driven agent called
“Daily Closing Update”
in my
Austin Mueller Palmetto
workspace. It’s been great so far, but I’m running into limitations around
model choice
and
timeouts
that I can’t control from the agent UI.
I’d love the ability to configure the following
per agent
from the Agent panel:
  1. Model configuration
- A visible
Model
picker in the agent profile (e.g., Fast / Standard / Advanced, or specific models like
GPT‑4.1
,
GPT‑4.1‑mini
,
GPT‑5.1
, etc.).
- Ability to tune
cost vs. speed vs. quality
per agent. For example:
- Use a cheaper/faster model for high‑frequency, structured automations like my Daily Closing Update agent.
- Use a higher‑quality model for more complex reasoning or drafting agents.
- Ideally, this setting would be:
- Editable only by managers of the agent.
- Visible in the UI alongside Name / Description / Jobs / Skills so it’s easy to audit.
  1. Timeout and retry configuration
- Per‑agent controls for:
-
Maximum run time
before an agent times out (e.g., 10s / 30s / 60s / 120s).
-
Retry behavior
(number of retries and backoff) when tools are slow or transiently failing.
- Clear
timeout behavior options
, for example:
- “Fail silently” (no user‑visible message, just logs).
- “Post a short error in a chosen location” (e.g., in the same chat, or as a comment on the task) when a run fails or times out.
- Surfacing timeout/abort reasons in the run history so it’s easier to debug agents that fire from automations.
  1. Configuration visibility & auditability
- A small
“Runtime” section
in the Agent panel that shows:
- Selected model.
- Max run time / timeout.
- Retry policy.
- This would make it much easier to reason about why an automation‑heavy agent is slow, timing out, or more expensive than expected.
These controls would really help me:
  • Optimize cost/speed for always‑on agents like my closing‑form automation.
  • Reduce flakiness from timeouts.
  • Debug and trust AI behavior in production more easily.
Thanks for considering this — happy to share more detail on my Daily Closing Update use case if that’s helpful.
Best,
Aditya