Calliope Journal

Field note

Choose ChatGPT, Claude, or OpenCode—and keep writing offline

Calliope separates optional online agent work from the local manuscript, saves, and Git history that remain available without a network connection.

A long manuscript outlives any single writing session, model release, or internet connection. That is why Calliope now supports three agent connections—ChatGPT, Claude, and OpenCode—while keeping the manuscript itself in local files on the writer’s Mac.

Agent choice and offline resilience are related design decisions. The agent should be a capable collaborator the writer can choose when it is useful, not a dependency that determines whether the manuscript can open, save, or retain its history.

Three supported agent connections

Calliope can connect a manuscript to ChatGPT, Claude, or OpenCode. A connected agent can work with manuscript content and structure through Calliope’s agent workflow: reading scenes, considering chapter context and metadata, proposing selected-text revisions, and helping organize a long project.

Supporting more than one agent environment gives writers practical flexibility. Some may already have a preferred account or workflow. Others may want to choose a different agent for a particular project. The durable project does not need to move when the connection changes; the manuscript and its Git history remain in the local Calliope project.

This does not mean that every agent is interchangeable. Models, account requirements, usage limits, and data practices vary by provider. Calliope’s claim is narrower: ChatGPT, Claude, and OpenCode are supported connection choices. It is not a promise that they produce identical results or operate under identical terms.

What happens when an agent is connected

The writer remains in the Calliope editor. When a task benefits from an agent, the writer can ask for analysis, organization, or revision in the context of the manuscript.

For a focused prose edit, that loop is deliberately inspectable:

  1. Select a passage and describe the requested change.
  2. Send the task through the connected agent environment.
  3. Review the proposed revision in context.
  4. Choose what enters the draft.
  5. Continue from a saved, recoverable manuscript state.

Broader agent operations can affect more than one passage, so durable version history matters alongside review. Calliope records saved manuscript changes in Git, making earlier states available for comparison and recovery.

What offline mode keeps available

Offline mode preserves the parts of the writing workflow that are truly local:

  • opening and editing the manuscript;
  • saving changes to local project files; and
  • creating local Git commits that record the manuscript’s history.

That means a writer can keep drafting on a train, in a remote cabin, during an outage, or simply with network access turned off. The current manuscript is still usable, and its local version history can continue growing.

Offline mode is not an offline AI feature. ChatGPT, Claude, and OpenCode connections are disabled without network access. Calliope does not claim that those services run locally on the Mac.

Git is local; GitHub is remote

The names are similar, but the roles are different.

Git is the local history system beneath the Calliope project. Local saves and commits can continue while offline. They preserve a sequence of manuscript states on the Mac and support comparison or recovery without contacting a server.

GitHub is an optional remote destination. When online, the writer can manually push local Git history to a private GitHub repository for off-device backup. Calliope does not automatically push when connectivity returns. In offline mode, GitHub features are disabled even though local Git history continues.

This distinction matters for honest backup expectations. Local Git can protect against a revision that does not work. It cannot, by itself, protect the project if the only Mac and its storage are lost. An online GitHub copy or another independent device backup addresses that separate risk.

A local-first boundary writers can understand

“Local-first” can become vague marketing language unless a product says what still works when the network disappears. Calliope’s boundary is straightforward:

  • The manuscript, editor, saves, and Git history are local.
  • ChatGPT, Claude, and OpenCode are optional online connections.
  • A manual push to a private GitHub repository is an optional online backup step.

This architecture lets a writer use ambitious agent assistance without making access to the manuscript conditional on that assistance. Going offline reduces the available tools, but it does not take away the draft or stop local version history.

Current status

Calliope remains in development for macOS. ChatGPT, Claude, and OpenCode are the supported agent connections in the current feature set. Public release timing, pricing, and final system requirements have not been announced.

The product facts page will continue to record these boundaries as the implementation changes. The standard is simple: agent capabilities should be described precisely, and the writer should always know which parts of the workflow are local, which require a connection, and which copy of the manuscript remains under their control.