Skip to main content
Open HowWorks

GPT-5.6 Terra

Bring an unfinished idea and work out what it wants to become.

Describe what you want to make, or drop a reference
Try a prompt:
GPT-5.6 Terra · 2026-10-21 · same reply · Q1/3

How should I prevent duplicate animation loops and input listeners when restarting a small HTML canvas brick-breaker game? Give a minimal lifecycle pattern, list the game state that must reset, and provide four checks that expose restart bugs. Do not produce a complete game or claim the pattern has been run.

Four restart checks: Restart ten times, then press Left once: paddle movement must be identical to a fresh load. Compare ball speed after each restart: it must not accelerate from multiple loops. Pause/restart during active power-ups: no old timer may alter the new game. Lose the final life, restart, then verify score, brick count, lives, and key state all match a new round. These are recommended lifecycle checks, not tested behavior.

View source
GPT-5.6 Terra · 2026-10-21 · same reply · Q2/3

How should a small React team choose between BlockNote and Tiptap for a Notion-style first version with paragraphs, headings, lists and reliable save-and-reload? Give a conditional initial choice, separate editor functionality from storage and permissions we must implement, and identify what must be verified before adding collaboration or comments.

Initial choice: choose BlockNote when speed to a conventional Notion-like editor matters more than bespoke interaction design. For paragraphs, headings, lists, and save/reload, its ready-made UI reduces first-version work; store its native JSON plus a schema/version field. Choose Tiptap instead when the product needs a strongly custom editing experience, custom node behavior, or a design system you expect to own deeply. Its headless architecture gives more control, but requires more UI assembly.

View source
GPT-5.6 Terra · 2026-10-21 · same reply · Q3/3

For an online-first issue tracker with occasional disconnects and concurrent edits, when should a small team use server-first optimistic updates rather than local-first sync? Explain retry idempotency, conflict handling, reload recovery and server-side authorization. Identify which scaling problems in Linear's August 2026 delta-sync article do not, by themselves, justify copying its architecture.

Each mutation needs a client-generated operation ID (idempotency key). Retrying after a timeout must return or safely recognize the original result, rather than creating duplicate issues, comments, or transitions. For concurrent edits, send an expected revision/version. The server should reject or flag stale writes; use field-level merge only where semantics are clear, otherwise present a conflict and require a deliberate choice. Do not silently let last-write-win overwrite critical fields. On reload, fetch the canonical server state, then reconcile any persisted, unacknowledged operations by operation ID. Mark irreconcilable operations as failed with a recovery path; do not assume browser memory is durable. Authorization is server-side: every mutation validates identity, workspace/project membership, object access, and transition rules. Optimistic UI is not permission enforcement.

View source

How it works

Try it now
  1. 01

    Say what you want

    A sentence or two is enough.

  2. 02

    Work with HowWorks Agent

    Describe the result you want. The Agent works with the tools you choose.

  3. 03

    Make it

    Start creating, then keep working with HowWorks.

GPT-5.6 Terra at a glance

Good at
Talk through ideas and shape your next draft.
Max output
128,000 tokens
Attachments
Images 20 MB · PDF 32 MB

About

An idea does not have to arrive as a complete prompt. Start with the audience, the problem you want to address and the material you already have. Ask GPT-5.6 Terra for meaningfully different directions, compare what each would say, then develop the most useful one into an outline. Add examples and constraints as the draft takes shape. Before using the result, check that it makes a specific point and does not introduce claims you cannot support. Terra handles the Agent conversation; any media creation uses a separate tool rather than turning a writing request into an automatic generation.

Questions

What should I provide before brainstorming?

Describe the audience, purpose and what is already known. Say what you want to avoid, such as a sales pitch, a familiar analogy or a topic you have already covered. Concrete constraints make the options easier to choose between.

How do I avoid three versions of the same idea?

Ask for alternatives with different premises or structures, plus the tradeoff of each. Select a direction for its message, then ask for wording; similar drafts can look different without saying anything different.

Can Terra revise a draft I already have?

Yes. Paste the text and identify what is not working: the order, argument, voice or ending. Ask it to preserve the strongest passages and explain substantial edits so you can decide what to keep.

Can the Agent make visuals for the idea?

You can ask the Agent to use an available creation tool once the brief is clear. Terra is the conversation model; an image or video tool has separate model choices, settings and charges.