Work with Atoll from the ChatGPT Command Center
Inspect connected agents and work, select compact context, follow stable links, and confirm issue creation in supporting ChatGPT hosts.
This combined record covers the Command Center, explicit context selection, deep links, Composer discovery, native issue forms and Working Set published on October 1, 2026, plus the agent-first Command Center from October 7. The original October 1 publication date remains. This page was consolidated on October 27; the October 7 capabilities arrived after the initial release.
Inspect connected agents and current work
Open Atoll in a supporting ChatGPT sidebar to see connected agents before choosing a profile. Filter by workspace or Needs attention, then inspect an agent's assigned issues and recent activity. The Command Center also provides authorized views of open human-attention requests, critical and warning Heartbeat signals, active executions, projects and issues.
Open-work totals read every issue page and multi-assignee link. Incomplete reads show a retry state instead of a partial count. Status labels follow each project's live workflow, and blocked work takes precedence. Totals across profiles count assignments; they do not imply unique issues, online presence or running executions.
Project views show current workflows and issues. Issue detail shows status and description; dependencies and activity load on expansion. Attention and execution links open read-only details. App reads use the selected connection-scoped profile_ref. A profile change clears previous workspace data before loading the new view.
Select compact context explicitly
Select projects or issues to share compact references with the current thread. Select several, remove individual items or clear the selection. References contain stable IDs, display names, the authorized profile and already-loaded workflow labels. They exclude issue descriptions, comments, Artifacts, repository files and conversation history. Browsing links or loading details does not add or promote selection context.
When authorization proves an item or profile unavailable, cleanup removes only affected Atoll references and their summary, preserving other selections and unrelated host content. Failed cleanup offers visible retry. A profile change clears previous Atoll selection without clearing unrelated host context.
Restored selections show saved identity first; load details for current data under the recorded authorized profile. If that profile is unavailable, choose one normally. Saved titles and statuses grant no access. Supporting hosts show Shared with ChatGPT only after acceptance. Unsupported hosts retain Local selection; failed updates offer retry. Selection sends no message, submits no prompt, changes no draft and writes no Atoll work.
The model receives versioned structuredContent.atoll references and must use existing tools with the recorded profile_ref and UUIDs to read current details before acting. The October 7 agent-first flow adds version 2 agent/issue context with version 1 compatibility: opening an agent shares its compact discussion scope when supported, opening an issue replaces that scope, and returning to All agents clears it. Unrelated host context remains intact.
Review a question before sending it
Discuss with ChatGPT opens an editable draft. Only Send to ChatGPT hands the reviewed question to the host through the explicit ui/message flow. Cancellation sends nothing. A rejected or unsupported send retains the draft for retry. The app sends identity and your question, without issue bodies, comments, activity text, Artifacts, credentials or a simulated reply.
Keep a local Working Set
In a supporting conversation panel, choose an authorized profile, search issues and projects, and pin work. Rows show current workflow labels, priority, assignees and known blockers. Expand dependencies or activity as needed. Refresh rechecks current data and permissions through existing read tools.
Adding or removing pins changes only the local panel. Explicitly focus one issue or project to share an active canonical reference; other pins remain local. Shared with ChatGPT, Local selection and In Working Set distinguish these states. Active appears only after host acceptance; unsupported or failed sharing stays local. Removing a pin does not remove an already-shared reference: use Deselect or Clear selection under Selection.
Each thread app instance has its own pins. Open details uses the canonical entity route, and returning keeps pins in that instance. A recreated panel can rebuild from current authorized context; unshared local pins are ephemeral. Working Set creates no thread record, sends no prompt and writes no issues or comments.
Follow stable links without changing authority
Deep links open a project, issue, attention item or execution by stable UUID, even after a rename. Internal links, host navigation and web-generated links share canonical routes. Later host links navigate the existing app without a reload. Choose an authorized profile before a destination read when several are available. Links grant no access, do not try another actor after denial and add no chat context automatically. Invalid paths show a safe error before any entity read.
Issue detail and project overview show Open in ChatGPT only when the web deployment has its published Atoll plugin ID configured. It opens a new tab and leaves the normal web page available. Without that configuration the action is omitted. Unsupported hosts retain ordinary sidebar and web navigation.
Find authorized entities from the Composer
Supporting desktop hosts can discover issues, projects, human and agent members, goals, KPIs and initiatives. Exact names and human issue identifiers rank before loose matches. Empty searches return a bounded first page. Results identify type, organization, profile and available project context; the same entity under two profiles retains two links.
Each resource read rechecks the exact OAuth grant and current entity permission. Results contain compact identity and state, exclude long histories, change no records and never switch actors after access denial. Composer discovery is a separate read-only extension; sidebar navigation and explicit context selection retain their own behavior.
Project, goal, KPI and initiative lists filter names on the server before pagination. CLI and ordinary MCP lists expose matching query and exact-name filters; member lists also accept visible member identity. Member and initiative lists can page across accessible projects without per-project requests. KPI pages retain current calculated values, and guest rules still apply. REST and ordinary MCP goal, KPI and initiative calls without search, exact, paging or scope options retain their legacy response shape. CLI context-conflict diagnostics redact API-key values while retaining non-secret source metadata.
Confirm one issue through supported native forms
Supporting registered desktop hosts can use two native forms to confirm a title, project, priority and dates, then select live project workflow, milestones and searched assignees. Cancel or decline either stage to create nothing. Final explicit confirmation rechecks access and current choices before one normal API creation. Notifications, webhooks and automation retain their usual behavior.
The plugin-only atoll_create_issue_interactive uses standard MRTR form elicitation and the OpenAI rich schema under protocol 2026-07-28. Signed state expires after ten minutes. Durable actor/org-scoped canonical create identity prevents a consumed form creating another issue, even after deletion of the original. For an uncertain result, check Atoll for that issue before a new attempt; automatic retries are disabled. Ordinary deterministic creation with complete values remains available. Unsupported hosts receive recovery guidance.
Check host availability and publication
The public plugin provides app-only atoll.open with empty input, a self-contained MCP App resource, atoll.working_set and the Composer search_mentions extension. Existing business tools and authorization remain unchanged. Browsing, context selection and pins do not move statuses, resolve requests or start executions. Requested writes use business tools or explicitly confirmed forms.
Native sidebar, context, links, Composer, forms and panel availability depend on the supporting host and published integration. Published-plugin configuration and signed-in desktop acceptance remain separate checks. Local URL, protocol and controlled-host verification do not prove provider acceptance or availability in every host. No mobile or Android workaround is included.