The whole workspace, from the assistant you already use
Connect your own AI client over MCP. It can do what an agent inside YATFA does — read the knowledge base, file a ticket, check a roadmap — within your account’s permissions. And the work still goes through the same review, QA and rules.
Knowledge/Background jobs
Project knowledge · v8
Background-job retry integrity
When prose promises a retry, grep the job class for its retry configuration — and prove it with the test adapter’s enqueue count.
Agents read it before related work — and so does your client
Tickets/AC-247
TaskAC-247Draft · waiting for your confirmation
Give the export job a real retry
Filed from your editor · linked to “Background-job retry integrity”
PathCode → Review → QA → your gateRulesAcme autonomy settingsSourceMCP · your account
ConfirmEdit
Roadmaps/Reports
Reports — one surface for what was delivered
Active · slice 3 of the direction in review
MergedAny date window · the trend follows itIn reviewMove the delivery chart off the dashboardNextCut after slice 3 lands
Wherever work starts, it takes the same path
A ticket filed from your editor isn’t a side door. It gets the same review, the same QA and the same autonomy rules as one filed in the web app — or one YATFA proposed itself.
Ticket AC-247
Give the export job a real retry
Filed from
PathConfirm→Code→Review→QA→Your gate
Reviewed byA different agent from the one that writes the code
Who approvesAcme’s autonomy settings — the same switches as for any ticket
KnowledgeLinked to “Background-job retry integrity”, read before the first commit
Switch where it came from. Only the first line changes.
It acts as you — never as more than you
Your client works within your account’s permissions. Flip the switch and ask it to approve a proposal.
Your account on Acme
What your client can do follows from what you can do.
You may approve proposalsOff — approvals go to someone else
Approve the proposal to split the upload validator.