Tabbit
ResourcesBlogModels
Tabbit LogoTabbit

Tabbit — The AI Browser that Works for You

Topics

  • Best Browsers 2026: Rankings and Top Lists
  • AI Browser Guides and Resources
  • Browser Comparisons: Head-to-Head Guides
  • Browser Reviews and Explainers
  • Browser Alternatives
  • Browser Directory: Guides by Browser
  • Agentic Browser Resources
  • Browser Downloads and Install Guides
  • Browser Productivity Resources
  • SillyTavern Model Guides and Presets

Popular Guides

  • Best Browsers 2026: Top 10 Ranked & Compared
  • Best Free AI Browsers 2026: Plans & Prices Compared
  • Rabbit Browser: What It Is & Why Tabbit Is Better
  • Firefox vs Chrome 2026: Privacy, RAM & Speed Compared
  • Best Lightweight Browsers 2026: 7 Tested for RAM & Speed
  • AI Browser List 2026: 10 Browsers Compared
  • Neobrowser: Norton Neo, Download & Alternatives
  • Edge vs Chrome 2026: Speed, RAM & Battery Tested
  • Best Internet Browser for Android 2026
  • Best AI Browser 2026: Top 9 Tested & Ranked

Events

  • Tabbit Skill Competition
  • KPOP SBTI Fandom Personality Test
  • Tabbit Campus Creator Program
  • fifi's Picks: AI Skills for Research Papers
  • User Survey

About

  • Tabbit Blog
  • Press & Media
English
简体中文English
Review
CommunityGPT-6.1 Terra

GPT-6.1 Terra Repeatedly Violates Progress-Reporting Instructions in ChatGPT Work: A User Report

Original source

Reddit, r/codex

Authoru/Hefestion89

Source date2026-10-26

Tabbit curation2026-10-26

Read original

One-sentence takeaway

A Reddit user reports that GPT-6.1 Terra repeatedly sent progress updates the user had explicitly asked it to avoid while evaluating a novel chapter by chapter in ChatGPT Work; the author says switching to the highest reasoning level did not noticeably help. The post provides no conversation logs or quantitative metrics, so it is not possible to distinguish model behavior from Work orchestration, session-specific factors, or an early-release issue.

Use cases

  • Tasks this report can inform: Understanding one user's experience with GPT-6.1 Terra following process constraints in a multi-step writing workflow in ChatGPT Work.

  • Claims this report cannot support: Generalizing about the model's overall instruction-following rate, literary-analysis quality, or other users' experiences, or determining whether the issue came from the model, client orchestration, or a single session.

  • Model version covered: GPT-6.1 Terra (the original post also calls it Terra 6.1).

  • Test environment or client: ChatGPT Work; the author did not specify the operating system, exact client version, novel file format, or session settings.

  • Reasoning level and parameters: The author started with Medium, then switched to maximum; other parameters were not specified.

Evaluation method

The author asked Work to read a novel chapter by chapter, record its analysis, and provide a comprehensive evaluation at the end. The author then proposed a step-by-step workflow: read one chapter at a time, add the analysis and conclusions to a working document, continue with subsequent chapters, and synthesize everything at the end. The author also asked it not to send progress reports and to deliver only the finished work.

The author says they repeated the instruction not to interrupt about five times, but Terra continued sending progress messages such as "Chapters 1–5 completed." The author first used the Medium reasoning level to observe efficiency and token consumption, then switched to the highest level in hopes of improving instruction following. The post does not identify the novel, provide the exact prompt, state the number of chapters or execution rounds, include conversation logs, or specify evaluation criteria.

Key results

  • The author's subjective report: Even after about five repeated reminders, the model sent another progress message; each time, it appeared to acknowledge the correction before repeating the behavior later.

  • The author says switching to the highest reasoning level did not noticeably improve instruction following and used up some usage allowance.

  • The workflow did not progress far enough to evaluate the literary analysis, and the author explicitly says they cannot assess its quality.

  • The author suggests this could be an early-release issue or an interaction between Terra and Work's agent orchestration, while acknowledging that session-specific factors cannot be ruled out. These are the author's hypotheses, not verified causes.

Raw data

  • Task: Read a novel chapter by chapter, record analysis and conclusions, and provide a comprehensive evaluation at the end; do not report progress in the meantime.

  • Reported constraint violations: The author says the behavior continued after about five repeated reminders; no turn-by-turn logs or independent count were provided.

  • Reasoning levels: Medium, then maximum.

  • Quantitative metrics: No success rate, number of chapters completed, analysis quality rating, response time, token count, or amount of usage consumed was provided.

  • Comparison: The author says they had previously used Work for large writing and document tasks, and had used GPT-6 and Sol 6.1 for more complex tasks; no controlled test with the same prompt, novel, or environment was provided.

Conclusions and limitations

  • This is a field report of one user's experience. It may suggest a test case for whether constraints persist through a long workflow, but it is not an independent benchmark or a general performance finding.

  • The post includes no original conversation, complete input, or working document, so it is not possible to verify whether the model behaved as the author describes or independently reproduce the reported behavior.

  • The author could not evaluate the literary-analysis results. The evidence in this post concerns only the progress-reporting constraint and does not support conclusions about literary-analysis ability.

  • The author's observation that switching reasoning levels produced "no noticeable improvement" is subjective; the number of task rounds, time spent, and duration at each level are not given.

  • The author raises possible early-release, Work-orchestration, and session-specific factors, but provides no evidence confirming the root cause.

Reproduction notes

The original post does not disclose the novel, full prompt, turn-by-turn conversation, working document, runtime, or reproduction steps, so the reported behavior cannot be fully reproduced from it. To verify the phenomenon, one would need to run a multi-chapter document task in ChatGPT Work with the same model version, record the complete conversation and original instruction explicitly prohibiting interim updates, note the reasoning level and each instance of deviation, and report the author's experience separately from measured results. No independent retest was conducted for this article.


Curated by Tabbit

This is a third-party source navigator. Model versions, test environments, and personal experience vary; consult the original source.

GPT-6.1 Terra

Use and compare models in Tabbit

GPT-6.1 Terra

Related reviews

OfficialOpenAI

GPT-6.1 Terra: OpenAI’s Official Benchmark Results and Capability Boundaries

OfficialOpenAI Deployment Safety Hub2026-10-26

GPT-6.1 Terra: Safety and Alignment Evaluations in OpenAI's System Card

OfficialHacker News2026-10-26

Hacker News: GPT-6.1 Terra's Model Selection and Technical Writing Boundaries

MediaArtificial Analysis2026-10-26

GPT-6.1 Terra: Artificial Analysis Intelligence Index and Cost Efficiency

GPT-6.1 Terra

Related prompts

OfficialOpenAI API documentation

GPT-6.1 Terra: Model Configuration and API Capabilities

OfficialOpenAI API documentation

GPT-6.1 Terra: Choosing a Model and Reasoning Level for the Task

OfficialAmazon Bedrock documentation2026-10-26

GPT-6.1 Terra: AWS Bedrock Setup and Tool Calling

OfficialOpenRouter2026-10-26

GPT-6.1 Terra: OpenRouter Routing and API Configuration