Summary
No way to insert a page break in a Google Doc via gog docs. The Docs API supports InsertPageBreakRequest directly, but it's not surfaced as a CLI subcommand.
Current state
gog docs --help exposes no insert-page-break / page-break / pb command- Markdown path doesn't help — markdown has no native page-break construct, and
gog docs write --markdown wouldn't know how to translate one
gog docs format operates on existing content; it can't insert new structural elements
Proposed shape
gog docs insert-page-break <docId> [--index N | --at-end] [--tab=STRING]
Single InsertPageBreakRequest against the segment.
Use case
Any multi-page deliverable — reports, decks-as-docs, multi-day itineraries with one day per page. Without page breaks, agents fall back to ASCII separators (e.g. ════════════), which look unprofessional in the rendered doc. Filed against the MCP wrapper as part of chrischall/gogcli-mcp#10.
Filed by Claude (AI agent) on behalf of @chrischall while expanding gogcli-mcp — an MCP wrapper around gogcli — to cover more of the upstream surface. The use case is real; please treat as a normal feature request.
Summary
No way to insert a page break in a Google Doc via
gog docs. The Docs API supportsInsertPageBreakRequestdirectly, but it's not surfaced as a CLI subcommand.Current state
gog docs --helpexposes noinsert-page-break/page-break/pbcommandgog docs write --markdownwouldn't know how to translate onegog docs formatoperates on existing content; it can't insert new structural elementsProposed shape
Single
InsertPageBreakRequestagainst the segment.Use case
Any multi-page deliverable — reports, decks-as-docs, multi-day itineraries with one day per page. Without page breaks, agents fall back to ASCII separators (e.g.
════════════), which look unprofessional in the rendered doc. Filed against the MCP wrapper as part of chrischall/gogcli-mcp#10.Filed by Claude (AI agent) on behalf of @chrischall while expanding gogcli-mcp — an MCP wrapper around gogcli — to cover more of the upstream surface. The use case is real; please treat as a normal feature request.