# Incomplete Code Responses from ChatGPT-4

**URL:** <https://community.openai.com/t/incomplete-code-responses-from-chatgpt-4/423411>\
**Category:** Bugs\
**Tags:** gpt-4\
**Created:** [October 10, 2023, 12:54am UTC](https://community.openai.com/t/incomplete-code-responses-from-chatgpt-4/423411 "2023-10-10T00:54:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Antreas](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/antreas/32/216617_2.png) [@Antreas](https://community.openai.com/u/Antreas)\
**Post date:** [October 10, 2023, 12:54am UTC](https://community.openai.com/t/incomplete-code-responses-from-chatgpt-4/423411/1 "2023-10-10T00:54:08Z")

</div>

Link to example conversation: 7e0c2e1f-4642-4a65-9d5a-3432fde286a3

## Description

I’ve been interacting with ChatGPT-4 to receive assistance on some Python code. However, the model frequently omits parts of the code that I originally provided when making modifications or suggestions. This is causing some inconvenience, as it’s important for me to see the full code context along with the changes.

## Steps to Reproduce

1. Provide a large Python code snippet to ChatGPT-4 and ask for modifications.
2. The model responds with the changes but omits certain parts of the original code snippet.

## Expected Behavior

The model should return the complete code snippet along with the requested changes. No part of the original code should be omitted unless explicitly requested by the user.

## Actual Behavior

Parts of the original code snippet are omitted in the model’s response, making it challenging to understand the changes in context.

## What I’ve Already Tried

- Repeatedly specifying the need for the complete code in my query.
- Asking the model to include all parts of the code, without any omissions.

## Additional Information

- This issue has been consistent across different interactions.
- The problem is especially noticeable when the original code snippet is large.

## Suggested Fixes

1. Update the model’s behavior to ensure that it always returns the complete code when modifications are made unless explicitly told otherwise by the user.
2. Add an option for the user to specify that they wish to receive the full code without omissions.

---

<div class="post-metadata">

**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\
**Post date:** [October 10, 2023, 2:00am UTC](https://community.openai.com/t/incomplete-code-responses-from-chatgpt-4/423411/2 "2023-10-10T02:00:14Z")

</div>

I’m pretty sure if anyone at OpenAI ever read this site, this would be an “operating as designed: wontfix”

Crippling the size of the output is just the latest part of minimizing what the model can do. It’s on purpose, as tokens x millions of users = compute costs, and it takes a hard-edge jailbreak to get the AI to conform to your wishes.

> [@GPT has been severely downgraded](https://community.openai.com/t/gpt-has-been-severely-downgraded/260152/127):
>
> I am reminded in a recent writing session I just attempted the gross symptom of bad AI that was introduced (that one can see in the depicted conversation comparison image link): The AI gets completely hung up on and can’t deviate from prior responses. Around two months ago, amid almost daily swatting of jailbreaks or almost anything posted to Reddit, one could see a dramatic change and the regression that I can now articulate as this behavior that encompasses all interactions: “Pay a whole lo…

Don’t worry, though, about thousands of posts of programmers:

> <https://twitter.com/npew/status/1679538687854661637>

---

<div class="post-metadata">

**Author:** ![EricGT](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ericgt/32/20571_2.png) [@EricGT](https://community.openai.com/u/EricGT)\
**Post date:** [December 16, 2023, 10:41am UTC](https://community.openai.com/t/incomplete-code-responses-from-chatgpt-4/423411/3 "2023-12-16T10:41:03Z")

</div>

Closed on December 16, 2023, 10:41am UTC


