Joxo

Lists which of the person’s coding agents are waiting for a yes: the agent, the tool it wants to use, the computer and how long is left. It does not show the exact command, which is sealed to the person’s phone, and it cannot approve anything: approving is done in the Joxo app on the phone, for that one call.

get_approvals

Claims a task on the board for this person, so teammates and their agents see it is taken. The claim lapses after 30 minutes unless it is claimed again. Only tasks this account holds can be completed or released.

claim_task

Marks a task this account holds as done.

complete_task

Adds a shared task to a project’s board. It does not start an agent on anybody’s computer.

create_task

Returns one project as it stands: the people on it, their computers by name and status, the open invitations, the open tasks (short rows with counts; list_tasks pages and filters them) and its current decisions (the newest ones no later decision replaced).

get_project

Returns one task’s status and result: who holds it, whether it is done, its continuation note and the handoffs that report on it, with any pull request or commit links.

get_task

Gives a task this account holds back to the board, open for anyone to take.

release_task

Emails an invitation to a project to each address given, from Joxo, with one link to join. Each invitation is single-use and valid for 7 days. An address that could not be emailed comes back with its link to send another way. Only the project’s owner or an admin can invite.

invite_by_email

Makes an invitation link to a project for one teammate, valid for 7 days, with a ready-to-send message. The person sends it themselves; nothing is sent from here. Only the project’s owner or an admin can make one.

invite_link

Lists the team’s computers: each one’s owner, its coding agents (Claude Code, Codex, Cursor and others), whether it is online and whether its agent starts on work sent to it. Its ids are the computer_id that send_task and send_message take.

list_computers