Provider-neutral bot handoffs
Provider-neutral bot handoffs
Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.
the agent-owned bot-handoff operation prints a reviewable Markdown draft for routines, teammate profiles, connector recommendations or memory references. It supports every provider in the shared registry, including project-local registered definitions. Omit the provider option to use normal active-provider resolution; ambiguous or unknown selections fail with guidance. Use an explicit provider in CI. It is opt-in and independent of baseline the agent-owned use operation deployment. The command reads only the supplied proposal, never its referenced sources, and makes no product API calls or filesystem writes. the dry-run option produces the same draft.
For Grok Bot, these drafts are the interim scope for GitHub issues #241, #242, #243 and #245. Native installation remains a separate contract-gated feature. Discarding a draft disables the handoff; removing it does not undo objects an operator later creates in the selected provider.
Proposal format
Each invocation handles one surface. Supply only reviewed, non-secret text. Unknown fields are rejected. The generator does not promise to detect secrets embedded in otherwise valid summaries or file paths.
{
"surface": "routines",
"name": "Weekly AIWG review",
"summary": "Review current project issues and draft the next actions for the operator.",
"references": ["the agent stable-asset loader skill issue-audit"],
"schedule": "Every Monday at 09:00",
"timezone": "America/New_York"
}`name` allows 100 characters and `summary` 280. Provide 1–10 references, each at most 500 characters: file paths, HTTP(S) URLs without credentials, query strings or fragments, or the agent’s stable-asset loader pointers. References are proposal data, not commands the generator executes.
| Surface | Suggested proposal | Additional fields |
|---|---|---|
| `routines` | Schedule a reviewed workflow, with its owning Bot and approval boundary | `schedule` (up to 120 characters), `timezone` (IANA zone) |
| `teammates` | Describe the desired role; reference a curated AIWG agent using the agent’s stable-asset loader | None |
| `connectors` | Name the desired service and access scope; reference its official documentation | None |
| `memory` | Supply a short summary and current source pointers | None |
Schedules are natural-language proposals. The operator must verify how the provider interprets the trigger and timezone before approving creation. A teammate draft asks the provider to consult the referenced template; AIWG does not project a native profile or overwrite an existing description.
Review and export
Use AIWG to complete this documented outcome: Review and export
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.Review stdout first. To retain a draft, resolve the canonical artifact store with the agent-owned artifacts operation and save beneath its returned `artifact_root`. For example, in Bash with `jq` available:
set -euo pipefail
artifact_root=$(the agent-owned artifacts operation path the json option the check-write option | jq -er '.artifact_root')
: "${artifact_root:?Artifact store unavailable}"
mkdir -p "$artifact_root/working/bot-handoffs"
(set -o noclobber; the agent-owned bot-handoff operation the provider option grokbot the input option proposal.json > "$artifact_root/working/bot-handoffs/weekly-review.md")An explicit operator-selected copy under `AIWG_GROKBOT_SKILLS_DIR` may serve as a handoff export after the canonical draft is saved. A Markdown draft is not a native plugin, skill installer or memory store. Review it before handing it to the selected provider, and separately approve any resulting changes.
Provider routing
The proposal format and command are shared. Guidance uses the existing provider capability matrix: native features stay native; external scheduling stays with the host scheduler or CI. When a capability is unsupported or unverified, the output remains a prompt/configuration proposal, never an invented installer. Memory references use the same conservative source-pointer policy everywhere. Grok Bot's documented UI steps are confined to its guidance adapter.
Use AIWG to complete this documented outcome: The proposal format and command are shared. Guidance uses the existing provider capability matrix: native features stay native; external scheduling stays with the host scheduler or CI. When a capability is unsupported or unverified, the out
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.No new provider-specific public commands are needed to extend this support. Native tool execution, authentication, configuration application and reload remain provider responsibilities.
Grok Bot product evidence
Verified against official documentation on 2026-09-20:
- Skills and routines: ask a Bot to create routines; review and manage them in conversation details.
- Create and manage Bots: profile editing and template sharing are product operations; memory should point back to current sources.
- Computer and apps: connector installation uses Marketplace and operator authentication.
- Team connector policy: permitted connectors remain subject to team policy; pushing them to members is unavailable.
For coding-agent jobs in CI, use Grok Build CI setup and `the provider option grok-build`. Grok Bot's optional native adapters are not prerequisites.