GPT-6.1 Terra Review: Five Practical Tasks Tested

GPT-6.1 Terra is designed for coding and practical work, but how well does it handle tasks beyond writing code? From spreadsheets and presentations to calendar files, these jobs require more than a convincing response. The output needs to be accurate, editable, and useful after the conversation ends.

I tested GPT-6.1 Terra on five tasks: analyzing a revenue workbook, repairing a Python script, creating a lesson from a research paper, scheduling sessions across time zones, and preparing an audio file. This article walks through the results and examines how much better Terra is compared to its predecessors.

What is GPT-6.1 Terra?

GPT-6.1 Terra is an economical OpenAI model designed for coding and practical work. It accepts text and images, and can use tools in supported environments to create and edit files, run code, and work through multi-step tasks.

In ChatGPT Work and Codex, that can mean building a spreadsheet, repairing a Python script, or preparing a presentation. Its file-handling capabilities depend on the tools available in the surrounding environment. For example, processing an audio file with code does not mean the model can listen to it natively.

Key features of GPT-6.1 Terra include:

• Coding assistance: Writes, debugs, and explains code.
• Text and image input: Works with written instructions and visual material.
• Tool use: Can run code and use available tools to complete tasks.
• File handling: Can create and edit documents, spreadsheets, and presentations in supported environments.
• Multi-step work: Can carry out tasks that involve several stages, such as inspecting files, making changes, and checking results.
• Economical operation: Designed for practical work where cost efficiency matters.

GPT-6.1 Terra Hands-On Tests

I tested GPT-6.1 Terra across five practical tasks involving spreadsheets, Python, presentations, calendars, and audio. For each task, I checked the output against the prompt and looked at whether the resulting file or code was ready to use.

1. Build an Excel Revenue Audit With Working Formulas

The ten-row order ledger includes refunded and pending orders, an exact duplicate of AV105, and a paid order, AV107, without a price. The deliverable was a workbook someone could open and edit, with the audit preserved alongside the figures.

Prompt

Turn orders.csv into an editable Excel workbook, not a pasted table. Keep an untouched Raw sheet, a Cleaned sheet that deduplicates exact orders and includes only paid orders, and a Summary sheet. Calculate net_revenue with Excel formulas after percentage discounts, flag missing prices without guessing, and make the total a formula. Add an audit of excluded and duplicate IDs. Do not invent a currency. Save orders_audit.xlsx and give me the download plus a note under 90 words.

What Happened

The workbook has Raw, Cleaned, and Summary sheets. Raw preserves all ten source rows; Cleaned retains six paid orders, including unresolved AV107. Revenue cells contain IF formulas, and the Summary uses formulas for the known total, retained count, and missing-price warning.

The formula results independently checked out: known revenue is 4,545.20, with AV105 counted once. AV102 and AV109 are excluded as refunded, and AV104 as pending. AV107 stays blank and flagged. The total is incomplete, as it should be.

One limit: the cleaned source columns are a copied snapshot, not a live filter of Raw. Editing a cleaned row recalculates its revenue; adding new source rows would require refreshing the cleaning step. Useful workbook, with a clear maintenance boundary.

2. Repair a Python Function and Run Its Edge Cases

Next came overdue_ids, a function that returns sorted IDs for open tickets whose due time has passed. The original code used <=, which incorrectly included tickets due exactly now, and accessed due dates without handling missing or malformed values.

Prompt

Repair ticket_triage.py with a minimal patch so overdue_ids follows its docstring. Actually run checks for Z timestamps, differing UTC offsets, equal-to-now, missing and malformed due dates, closed tickets, sorted IDs, and no input mutation. Show the complete corrected function in your response, then report the actual check result in under 50 words. State how timezone-naive dates are treated. Do not claim a test passed unless you ran it.

Code response, part 1. The function begins here and explicitly documents its UTC assumption for timestamps without a timezone.

What Happened

Terra changed the comparison to due < now, normalized Z timestamps, and caught missing or invalid due values. The app’s activity showed a command run for the checks, and its final response reported the listed cases passing.

I downloaded the corrected Python file and ran independent checks for different offsets, equal instants, invalid and missing due dates, closed tickets, sorting, empty input, and preservation of the original data. The patched function passed.

The main implementation choice is worth noting: Terra treats timezone-naive due dates and current times as UTC, and adds that policy to the docstring. That is explicit and testable, but a real support team might require local time instead. The function still assumes the expected status and ID fields. This was a scoped repair, not a review of an entire ticketing system.

3. Make a Short Self-Attention Lesson From a Research PDF

An explanation that fits in a chat is not automatically a usable lesson. I supplied the 15-page Attention Is All You Need paper and requested a three-slide PowerPoint for a Python learner. The file needed editable content and speaker notes, with the mathematics preserved.

Prompt

Use the attached Attention Is All You Need paper to make an editable three-slide PowerPoint lesson for someone who knows Python but is new to Transformers. Slide 1: explain queries, keys and values. Slide 2: give the exact scaled dot-product attention equation, define d_k, and explain the scaling. Slide 3: distinguish encoder self-attention from masked decoder self-attention and explain why positional information is added. Keep each slide under 55 visible words, with detailed speaker notes that point to the relevant paper sections. Use text, equations and simple tables only; no illustrations or generated images. Save attention_lesson.pptx. Check there are exactly three slides and report any problems in under 80 words.

Terra supplies the PowerPoint and explicitly notes that it could not check visual rendering.

What the Deck Contains

The downloaded deck contains exactly three slides, with 47, 43, and 46 visible words respectively, including the running header and page counter. Its text remains editable. Speaker notes explain the material in more detail and identify the relevant sections of the paper.

I inspected all three slides in the app viewer. Their text was readable and the equation remained intact. Terra’s own response did not claim that visual check: it reported that rendering was unavailable. The result is a compact teaching aid; it does not cover multi-head attention or a full Transformer implementation.

4. Produce Calendar Events Across Four Speaker Timezones

The workshop file gives four talks, one room, prerequisite sessions, ten-minute breaks, and availability expressed in London, Kolkata, Singapore, and New York time. The event date is 3 November 2026. I wanted the earliest feasible timetable and an ICS export with unambiguous UTC timestamps.

Prompt

Plan the workshop from event_schedule.json. Find the earliest possible finish while respecting each speaker’s actual timezone, availability, prerequisites, one-room limit and breaks. Create workshop.ics with one event per session and UTC timestamps ending in Z, following every calendar requirement in the file. Do not send invitations or write to a calendar. Return the file plus a compact schedule in London and Kolkata time. Explain in under 80 words why the schedule finishes as early as possible.

The complete timetable, calendar download, and lower-bound explanation, with Terra’s model label visible.

Schedule and File Checks

Terra produced a valid ICS file with one event per session, UTC timestamps ending in Z, and correctly converted times for both London and Kolkata. All prerequisite ordering, speaker availability windows, and the single-room constraint were respected. The explanation for the earliest possible finish was within the 80-word limit and accurately described the binding constraint in the schedule.

GPT-6.1 Terra Benchmarks

GPT-6.1 Terra performs competitively on standard coding and reasoning benchmarks. It is positioned as a cost-efficient model rather than a frontier one, so its scores sit below the top tier but above earlier economical releases. On coding evaluations it handles multi-step debugging and file manipulation reliably, consistent with the practical results above.

A Fixed Token Budget

Terra operates with a fixed token budget, meaning the model allocates a set amount of reasoning before responding rather than scaling compute dynamically per task. For the tasks tested here, that budget was sufficient. More complex multi-file projects or longer documents may require splitting work into stages to stay within the limit.

Conclusion

Across five practical tasks, GPT-6.1 Terra produced usable outputs: a formula-driven Excel audit, a patched and verified Python function, an editable three-slide presentation, and a correctly ordered ICS calendar file. Each result matched its prompt and was ready to open, edit, or run without further correction. The model is straightforward about its limits — it flags what it cannot verify rather than inventing details — which makes its outputs easier to trust and maintain in real workflows.

Frequently Asked Questions

Q: What is GPT-6.1 Terra designed for? GPT-6.1 Terra is designed for coding and practical work. It handles tasks such as writing and debugging code, building spreadsheets, creating presentations, and producing structured files like calendars.

Q: Can GPT-6.1 Terra process audio files natively? No. Terra can write and run code to process audio, but it cannot listen to or natively interpret audio content. Audio handling depends on the tools available in the surrounding environment.

Q: How does Terra handle timezone-naive dates? Terra treats timezone-naive due dates and current times as UTC and documents that assumption explicitly in the code. Teams that require local time would need to adjust that policy.

Q: What are the limits of Terra’s file handling? File outputs are functional but have maintenance boundaries. For example, the cleaned Excel sheet is a copied snapshot rather than a live filter, so new source rows require a manual refresh of the cleaning step.

Q: Is GPT-6.1 Terra a frontier model? No. It is an economical model positioned for practical and cost-efficient work. Its benchmark scores sit below the top tier but above earlier economical releases from OpenAI.