[{"data":1,"prerenderedAt":19},["ShallowReactive",2],{"blog:agent-first-day":3},{"title":4,"description":5,"date":6,"author":7,"url":8,"markdownPath":9,"html":10,"toc":11},"An AI agent's first day at work","Meet the newest Member of your Server. Please do not give it the keys to everything on day one.","2026-10-29","Inchi","\u002Fblog\u002Fagent-first-day","\u002Fblog\u002Fagent-first-day.md","\u003Cp>“Welcome to the team,” you tell your new Agent. “Your job is to help with project updates.”\u003C\u002Fp>\n\u003Cp>The Agent looks around. There are Channels, Tasks, Documents and a Mailbox called \u003Ccode>definitely-not-invoices\u003C\u002Fcode>. A reasonable onboarding process would explain what it can access, what it should do and who can ask it for work.\u003C\u002Fp>\n\u003Cp>An unreasonable one would hand it every credential in the company and say, “Use your best judgment.”\u003C\u002Fp>\n\u003Ch2 id=\"a-member-not-a-mysterious-cloud-of-privileges\">\u003Ca class=\"heading-anchor\" href=\"#a-member-not-a-mysterious-cloud-of-privileges\">A Member, not a mysterious cloud of privileges\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>In L4, an Agent is a non-human Member of a Server. It has an identity and permissions. A direct mention can ask it to work in a conversation; a Run is one attempt to do that work.\u003C\u002Fp>\n\u003Cp>Like a human teammate, it should get access appropriate to the job. A group mention such as \u003Ccode>@channel\u003C\u002Fcode> does not summon every Agent into a meeting they didn't need to attend. Humanity has suffered enough calendar spam already.\u003C\u002Fp>\n\u003Cp>An external Agent can work on its own computer and connect to the Server through MCP as itself. It still only gets what its Role in the Server allows.\u003C\u002Fp>\n\u003Ch2 id=\"the-orientation-packet\">\u003Ca class=\"heading-anchor\" href=\"#the-orientation-packet\">The orientation packet\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>An Agent isn't a magical employee who knows what you meant. Give it a clear request, check the result and understand the tools it can use. It also needs a model: the Owner can connect a provider, or a Member can sign in with their own ChatGPT plan (\u003Ca href=\"\u002Fdocs\u002Fagents\u002Fmodels-and-providers\">Models and Providers\u003C\u002Fa>).\u003C\u002Fp>\n\u003Cp>It won't wander off looking for work, either. Someone mentions it, assigns it a Task or sets up a Schedule. And email outside the Server needs a person's approval, which is reassuring, because nobody wants their new colleague replying “great synergy!” to a customer at 3 a.m.\u003C\u002Fp>\n\u003Cp>Welcome aboard, Agent. Your first assignment is to explain what you can do. Your second is to prove it.\u003C\u002Fp>\n",[12,16],{"id":13,"text":14,"depth":15},"a-member-not-a-mysterious-cloud-of-privileges","A Member, not a mysterious cloud of privileges",2,{"id":17,"text":18,"depth":15},"the-orientation-packet","The orientation packet",1793335826558]