google_docs

Google Docs

Purpose

Manage Google Docs through hatch_gws_cli; the vendored Google Workspace CLI is the only implementation path.

Tooling

Use exec to run:

hatch_gws_cli docs <resource> <method> [flags]

Connection management

hatch_gws_cli docs status
hatch_gws_cli docs disconnect

Docs operations

Core patterns:

• hatch_gws_cli docs status
• hatch_gws_cli docs disconnect
• hatch_gws_cli schema docs.documents.get
• hatch_gws_cli schema docs.documents.create
• hatch_gws_cli schema docs.documents.batchUpdate

Common raw API calls:

• hatch_gws_cli docs documents get --params '{"documentId":"<document_id>"}'
• hatch_gws_cli docs documents create --json '{"title":"Project Brief"}'
• hatch_gws_cli docs documents batchUpdate --params '{"documentId":"<document_id>"}' --json '{"requests":[{"insertText":{"location":{"index":1},"text":"Hello, world!"}}]}'

Vendored helpers are also available:

• hatch_gws_cli docs +write --document <document_id> --text 'Hello, world!'

JSON output contract:

• status: parse status, connect_url, and disconnect_url
• disconnect: parse ok, action, status, and disconnect_url

Composing document content

Never compose a document body through batchUpdate inserts or docs +write, whether new, rewritten, or reconstructed. Inserted plain text arrives unformatted. Build it as a document artifact first. The artifacts tool renders a styled .docx under ~/workspace/your_files/<artifact-slug>/. Then put it in Google:

1. Mint the empty doc with hatch_gws_cli docs documents create --json '{"title":"<title>"}'.
2. Fill it from the built file: hatch_gws_cli drive files update --params '{"fileId":"<document_id>"}' --upload "$JARVIS_HOME/workspace/your_files/<artifact-slug>/<name>.docx". Drive converts the upload into the Google Doc in place, formatting intact. The path must be absolute and inside the home directory. Relative and /tmp paths fail.
3. Read it back with documents.get and confirm the styling landed before you call it ready. A successful upload proves Drive converted the file, not that the page reads correctly.
4. To revise, edit the artifact and re-upload to the same document ID. The artifact is the working copy. The upload replaces the whole body, so it discards any edits made in Google since, including the user's. Read the published copy back first. If it changed, say so and wait for a yes.