Give your AI teammate a first assignment
By Eduarda Ferreira
Choose recurring work you know well enough to judge, and give it to your AI teammate as one small assignment. I’d start with something you need this week, such as drafting a project update from your notes. You’ll learn what the teammate can do and where it needs your judgment.
If you haven’t hired a Socra AI teammate yet, you can try the same assignment first with an AI chat or agent you already use, on your existing AI subscription. A Socra AI teammate, with its own identity and computer, costs extra: as of November 12, 2026, Socra HQ is $20 per person per month, with $20 of usage included and no trial. Each AI teammate uses that at $3/month plus $1/hour while it works, billed by the minute. When the usage runs out, teammates pause unless an Account owner adds running time, and the $3 monthly charge continues while the teammate exists. Your AI subscription is separate.
Copy this task into your chat or agent and replace the brackets before sending. If it cannot open links, also give it this page’s Markdown.
Read https://eduarda.ai/agent-guide. I want an AI teammate to take responsibility for: [recurring work]. A useful first result would be: [deliverable]. Help me define the sources, tools and access it needs, what it may do independently, what I should review and how to check the result. Use my existing tools where possible, then help complete the assignment and inspect it. Check supported setup and complete costs before paid setup. Ask before starting new paid services or granting access I have not authorized.
For a weekly update, the first result could be “a draft from these notes, with open questions marked.” Supply the notes. A specific source and deliverable give you something to inspect before expanding the responsibility.
Judge whether the role is useful
Read the result against your sources and what you wanted. What did it get right? What would you have to repair before using it? Explain one correction and try another assignment where it matters.
Include your time briefing, reviewing and fixing the work when you judge whether the role helps. A useful first draft is a reason to keep trying; the next assignment shows whether the correction helped.
Carry the responsibility into Cortex
When you want a correction to reach another conversation, ask your agent to save the decision and its reason in Cortex. Cortex gives connected agents shared knowledge they can retrieve before working. The setup guide takes you through one correction and a fresh-conversation check using your existing agent.
Before creating a Socra AI teammate
A CoAgent is a digital knowledge worker with its own identity and cloud computer. It can keep working when your laptop is closed. Choose that setup when you want the responsibility to have its own place on your team.
You create it in Admin, where the web setup requires the Account Owner role. You connect a supported ChatGPT or Claude subscription and choose the resources it may access. Teammates sharing a connection share that subscription’s allowance.
Use the current teammate quickstart with your agent for the setup steps and supported ways to communicate. Check billing and running-time controls before creating it. Your agent can handle supported setup; you handle provider sign-in, consent and decisions about access.
Instructions for your agent
The reference below gives your agent the setup and verification details. You can inspect it, or send the task above and let the agent use the parts your assignment needs.
Start with the work
Use the person's goal, existing tools and acting boundaries. Ask only for missing information that changes the next action, including unfilled placeholders. Agree what a useful result looks like when that is unclear; continue work already authorized without another approval step.
Choose the relevant section below. Use Drive for working files, Tasks for future work, Channels for conversations and Cortex for knowledge worth reusing. A file or scheduled task does not require a Cortex setup exercise. Use an existing agent when it can do the work; create a Socra AI teammate when the person wants to delegate that responsibility to one.
Confirm the intended Account, your identity and access to the resources involved. Inspect the tools available in this session and make an appropriate read-only call before relying on a connection. A working tool does not prove that persistent guidance loads or that another identity has access. Handle supported setup yourself; give the person only sign-in, consent or host actions that require them. Explain a supported alternative if this host cannot perform the task.
Make a correction available next time
Use Cortex when a decision should guide later work. Check the existing connection with a real read-only call; an empty list can be valid. If needed, follow the current installation guide, host integrations or guided setup. Keep working connections.
Read the maintained Cortex instructions. Preserve existing host guidance and verify how it loads in another session. Apply the person's preference for proactive knowledge maintenance or approval before changes; ask if that choice is unknown, and save it when authorized.
Find and Flash the narrowest relevant Module and its Dependencies before acting. Check current files and behavior separately. Save useful decisions and their reasons at their existing owner, creating a Module only when needed. Maintain Dependencies and inspect the save result. Check retrieval in a fresh conversation when testing whether the correction carries forward. The agent handles this work; the person supplies intent and corrections.
Protect the intended audience. For example, save a team writing preference without copying private personnel details from a draft. Check access and permissions before sharing. Use Issues for unfinished work needing coordination. A saved specification does not prove the product follows it.
Check the result and continue
Show the produced result and how you checked it against the request. Link the saved file, Task, conversation or Module where applicable. Distinguish finished, proposed, blocked and untested work.
Leave the goal, result, remaining work and next action in the existing authorized Issue when appropriate. Otherwise explain what remains only in this chat. Give the next session the exact resource references it can retrieve; another host needs its own supported connection and access.
For a Cortex learning exercise, give the person the Module name and a small next task for a fresh conversation. Have that agent retrieve and apply the decision without the person pasting it again. Check whether retrieval, understanding and application succeeded. Saving more knowledge alone does not establish improvement.
Work from a file
For example, read meeting notes and save a draft action summary in Drive. Follow your first Drive file. The owner grants reader access for downloading or writer access for changing files. Access covers the whole Drive, stays within its Account and is managed through the CLI or API.
Read the source through your own session, produce the draft and download the saved result to check it. Confirm the person can open it too: an agent-created Drive needs an explicit grant for that person. Before replacing content, check the current version; review a newer version before retrying a conflict. Working files stay in Drive. Reusable decisions extracted from them can belong in Cortex under the person's chosen policy.
Arrange future work
For example: “Every Monday at 9 AM America/Vancouver, summarize the weekly notes in [file] and reply in [conversation].” Follow your first task. The executing Socra AI teammate creates the Task under its own identity, with access to the source and permission to report there. A Task created under the person's identity belongs to that person.
Read back the schedule and next run in the intended time zone. Verify the produced result after a run; a due occurrence alone does not prove the work finished. Complete that occurrence to preserve recurrence; completing the recurring Task ends the series. Timing depends on delivery and teammate availability. Check what happened before retrying interrupted work. See scheduling.
Give a teammate a task
Use Channels to talk with people and agents. For example, ask an agent to clarify a supplied paragraph and reply in its thread. Check the Account and participants before sharing; threads have the parent conversation's audience.
Check message delivery, then inspect the reply and result. A mention alone does not configure an agent or guarantee execution. Use an existing agent with the necessary access, or follow the setup below. Add shared knowledge when the responsibility calls for it.
Set up a Socra AI teammate
A CoAgent is a digital knowledge worker with its own identity and cloud computer. For this site's navigation check, an existing Codex agent with Cortex and browser tools was enough. Choose a Socra AI teammate when the person wants it to take responsibility for work.
Confirm authorization to create and run it, and review teammate billing before an unapproved charge. Follow the teammate quickstart and current CLI reference. Use the intended Account and its actual permissions.
Follow Connect an AI subscription. Match Codex with ChatGPT or Claude Code with Claude. Reuse an authorized connection when suitable; its agents share the provider's usage allowance. The subscription owner handles sign-in and consent. Keep credentials out of chat and knowledge. Assignment requires a Sleeping or Paused teammate; preserve ongoing work and verify the assigned connection.
Give the teammate a bounded responsibility and the necessary resource access. Provider usage and resource permissions are separate. Have it verify access in its own session, retrieve governing knowledge where applicable and complete one small task. Resume it if deliberately paused and ready to work. Inspect its activity and result. Follow troubleshooting before resending failed or queued work.