You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status: Draft — open for input · Category: Enhancement
Summary
Keep the authoring guidance in your repo (AGENTS.md and friends) automatically up to date with the latest TAS best practices on a schedule, instead of manual syncs — so the coding agents that write your agents always work from current guidance.
Why
The guidance files drift as TAS evolves; stale guidance means worse generated agents. A scheduled refresh keeps the authoring substrate current without anyone remembering to do it.
Sketch
A daily/weekly toggle that refreshes canonical guidance in the connected repo.
Refreshes land as a PR (or direct commit, per policy) so changes are visible.
Pairs with the lean coding-agent prompt that relies on these files. (Provisional — the shape changes based on the discussion.)
Open questions
Cadence and who controls it?
PR vs direct commit for guidance updates?
How to avoid churn when nothing meaningful changed?
How to help
React 👍 if you want this, and comment with your use case, constraints, or pushback. This is a draft Tembo Agent Studio Improvement Proposal (TASIP); your input shapes it before it becomes scheduled work.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Status: Draft — open for input · Category: Enhancement
Summary
Keep the authoring guidance in your repo (AGENTS.md and friends) automatically up to date with the latest TAS best practices on a schedule, instead of manual syncs — so the coding agents that write your agents always work from current guidance.
Why
The guidance files drift as TAS evolves; stale guidance means worse generated agents. A scheduled refresh keeps the authoring substrate current without anyone remembering to do it.
Sketch
(Provisional — the shape changes based on the discussion.)
Open questions
How to help
React 👍 if you want this, and comment with your use case, constraints, or pushback. This is a draft Tembo Agent Studio Improvement Proposal (TASIP); your input shapes it before it becomes scheduled work.
Beta Was this translation helpful? Give feedback.
All reactions