Guides

sessions

Whether each account's saved session still works, from the platform's own answer, with the next step to sign it back in; and log's own sign-in for a team (login, logout, whoami).

Load next, when the work needs it: getGuide({ topic: "accountBrowser" }) (An account's one browser on any platform: opening it through its gates, inspecting a page step by step, where every open browser is, the live view for signing in, AdsPower profiles and local accounts); getGuide({ topic: "accountsAndProxies" }) (Every account in the workspace with its session state, and each account's proxy: checking it, giving it one from a provider in its home city, and providers' traffic; and the interactive launcher that sets log up and adds accounts).

Written by bun run docs:build from the code, the skills and AGENTS.md. Not edited by hand: change the command's usage, its skill or the rule, and rebuild.

Use cases these tools are part of

When the owner asks for one of these, follow its page step by step.

Use caseWhat it isHow the owner asks for it
getGuide({ useCase: "inbox/signIn" })Signing an account in: checking it, then the live browser"sign in to my account", "is my x account logged in", "check my accounts", "log me back into instagram", "my session expired", "check the status of my accounts", "open the browser so I can sign in", "sign into my discord account", "sign me in", "log me in here", "open the browser in the chat", "show me the browser", "log me in in hermes"

The tools in this guide

Each tool's own description carries its full usage, notes, live line and rules; logGet gives its exact inputs and a call that works.

ToolWhat it doesUsage
logoutForget the stored Twenty sessionlog logout [--apiUrl <url>] [--json]
whoamiShow who is signed in to Twenty, refreshing the session if it expiredlog whoami [--apiUrl <url>] [--json]
sessionsCheckCheck every account's saved session through its platform's own answerlog sessions check [--platform <p>] [--account <accountName>] [--json]
sessionsSignInSign an account inlog sessions signIn --account <account> [--platform <p>] [--route browser|cookies] [--done] [--wait <s>] [--open] [--json]

The rules these tools fall under

Each by its number and first line. The full text is in AGENTS.md (log://agents); the core rules are in full in getGuide({ topic: "logMcpInstructions" }).

  • Rule 25. Fix failed or unfamiliar behavior from its own recorded action/request/response timeline.
  • Rule 30. Complete the authorized task.
  • Rule 38. Do not introduce discussions of Meta/Facebook rules, terms, eligibility or account ownership unless The owner raises them.
  • Rule 39. Use only the scope, options and intent The owner stated or implied.
  • Rule 40. Do not propose physical infrastructure unless The owner asks.
  • Rule 41. Paid work must stay within the authorized task and spend.
  • Rule 73. For an unknown platform state, collate the goal, account/runtime, action, sent requests, answers, timing and page evidence.
  • Rule 94. Every platform call goes through Log and its governor, never a scratch client with account tokens/cookies.
  • Rule 163. Agent Log actions go through Log MCP tools; never work around a stale or unavailable MCP with shell Log commands or scratch clients.