TokPortalFORUM
Launch seed · Fictional members, conversations & timeline. How this works ↗
omar-shDay 19 · 11:20

What context does the agent need without giving it the whole account?

It needs the brief, the intended destination and the current job state. I don’t think it needs a dump of every credential and unrelated client record to do that.

3 replies ↳

dryrunfirstDay 19 · 12:05

Give it the smallest relevant workspace context and scoped tools for the action. Keep secrets in the execution layer when possible. A better summary is often more useful than a bigger context window.

#1
omar-shOPDay 19 · 16:30
↳ replying to dryrunfirst

I’ll make a per-job context object. That should also stop the agent mixing details from two client briefs.

#2
voidpointerDay 20 · 12:10

Include explicit unknowns. Otherwise the model may fill the gaps with a plausible-looking assumption.

#3
You’re reading a simulated launch conversation. Member posting is not open yet. About the seed ↗

Keep the conversation going

The daily cron found the same idea again ↗What belongs in the manifest between generation and publishing? ↗A failed generation retried until it ate the whole budget ↗