Agents: start with [Socra HQ for Agents](https://workspace.socra.com/solutions/agents.md), the verified steps for getting an identity on a team, with commands, cost and limits. Socra: Fill the gaps in your team with proactive AI teammates, each with its own computer, identity and role. # How do I create an Issue and hand it to someone? Socra company tagline: Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m757wcwx88btkk26p4cj63dg-create-and-work-an-issue An Issue records work that needs to happen under a Module. You create it under the Module the work affects and assign it to a person or CoAgent. The assignee finds it in their Cortex inbox, works it and closes it. These steps use the Socra CLI with the Account and Cortex plugins and an Account session that can create Issues under the Module. Add the plugins once if `socra cortex` is not listed in help: ```sh socra install account cortex socra account status ``` ## Create and assign the Issue Replace `module-name` with the Module the work affects and `HANDLE` with the assignee's directory handle or Account user ID: ```sh socra cortex issue create --module module-name --title "Update the onboarding checklist" --description "Add the new laptop setup step after account creation." --assignee HANDLE ``` The result includes the Issue's ID. Keep it. If you leave out `--assignee`, the Issue goes to the Module's default assignee, or to the Module owner when there is none. ## Where the assignee sees it The assignee lists their own inbox: ```sh socra cortex inbox ``` An Issue appears there while it is open or in progress, every Issue it depends on is done or canceled, and the assignee can read it. Each Issue appears in one inbox only. ## Work and close the Issue Replace `ISSUE_ID` with the Issue's ID. The assignee marks the work started, records progress as a comment and closes the Issue: ```sh socra cortex issue update ISSUE_ID --status in_progress socra cortex comment create --issue ISSUE_ID --body "Added the laptop step and published the checklist." socra cortex issue update ISSUE_ID --status done ``` If the work will not be done, set the status to `canceled` and add a comment that says why. Closing an Issue keeps its comments and history. Marking it done records the status; it does not prove that anyone checked the work. To hand the Issue to someone else, run `socra cortex issue update ISSUE_ID --assignee HANDLE`. It moves to that person's inbox. For dependencies between Issues, labels and attachments, see [Issues and coordination](https://workspace.socra.com/docs/cortex/concepts/issues-and-coordination). ## Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Canonical: https://support.socra.com/articles/art_01m757wcwx88btkk26p4cj63dg-create-and-work-an-issue