fix: Docker default non-interactive mode for Cloud instances

[rarepepi]

Relates to:

No linked issue.

Risks

Risk Level: Low
Adding a new flag non-interactive that defaults to skipping chat() should not affect existing functionality unless explicitly enabled. The main risk is around unintended bypass of user input under edge cases.

Background

What does this PR do?

This PR adds a non-interactive flag to prevent running the chat() function and avoid waiting for user input. This is particularly useful for environments such as Cloud platforms where interactive sessions are not feasible and can cause the application to hang.

Additionally, the non-interactive flag is added to the CMD in the Dockerfile as the default.

What kind of change is this?

Features (non-breaking change which adds functionality)

Why are we doing this? Any context or related work?

Running the application in a non-interactive environment such as Cloud platforms caused the process to hang due to waiting for terminal input. Adding this flag makes the application more robust for deployment in such scenarios.

Documentation changes needed?

My changes do not require a change to the project documentation.

Testing

Where should a reviewer start?

• Review the changes in the Dockerfile for the updated CMD with the non-interactive flag.
• Review the changes in /agent/src/index.ts where the non-interactive flag is implemented and its logic for skipping chat().

Detailed testing steps

1. Run the application locally without the non-interactive flag and verify that chat() runs as expected.
2. Run the application locally with the non-interactive flag and confirm it bypasses chat() and does not wait for user input.
3. Build and run the updated Docker image to ensure the non-interactive flag is applied by default and prevents hanging in Cloud environments.

Deploy Notes

No special deployment steps are required. Ensure the updated Docker image is pushed to the appropriate registry.

Database changes

None.

Deployment instructions

Build and deploy the updated Docker image as usual.

---

Let me know if anything else needs tweaking! 😊

[odilitime]

One additional note from chat, this helps with AWS ECS deployments

[rarepepi]

One additional note from chat, this helps with AWS ECS deployments

Fly.io deployments as well

[shakkernerd]

I really like this.
Thanks for adding it in!

[shakkernerd]

A very good feature to have.