No automatic syncing is easy to work around, but when you Upload This or Download Latest, you're firing blind — I propose a warning for when the file on-server has changed since download.

Can you add some kind of AI integration like a Chat Agent.
Look at VSCode. it allows you to add CoPilot, Claude, Codex etc

Then we could set up a proper AI framework like OpenSpec?

https://github.com/Fission-AI/OpenSpec

https://medium.com/coding-nexus/openspec-a-spec-driven-workflow-for-ai-coding-assistants-no-api-keys-needed-d5b3323294fa

This allows you to add Gemini level AI functionality that is correctly remembered and self updating.

Currently my work flow is;

Google AI mode -> TextTastic -> Working Code

The problem with using raw Google AI mode [Gemini] is that often your previous conversation gets too long and the context window crashes and you lose the entire conversation.

It only needs to be single agent driven, at the moment. Nothing too fancy. Just some way for an AI to traverse the project root and understand a project as it evolves. In this way, AI can add instruction files to every root folder. This acts like an index in a database. It tells the AI what this folder’s functionality & context within a larger application, is.

I was just looking at OpenSpec. Because it is a CLI that requires global node library installation, you may actually need to integrate OpenSpec into the App, itself. Obviously, iPhones cannot install NodeJs & Node libraries etc So there needs to be some deeper level integration, here.

IMHO, OpenSpec is currently the best & easiest AI spec framework, to work with.

This would be a massive win for TextTastic as a future proof, smart phone IDE.

Imagine being the only app in the world to have integrated a Spec framework, into its AI capabilities.

Why can't I open the .pgn files that I used to always create?

I have family sharing on iCloud enabled yet when my partner tries to sign in and restore purchase it simply will not work, enter password, and dialog box disappears. Can you please advise.

Thanks

Opened a One-Drive text file and worked on it a few hours then closed it as I have previously, expecting file to auto-save. When i re-opened the file all of my work was gone. Has the auto-save functionality changed?

Device: iPad Pro 12.9-inch (5th generation)

OS Version: iPadOS 26.3 (23D127)

App Version: Textastic 10.9.2

Accessibility Feature: Voice Control (hands-free use)

Summary:

Voice Control fails to correctly deliver text input to Textastic's terminal view. This issue has persisted across two iPadOS updates, first observed on January 25, 2026, and remains unresolved as of iPadOS 26.3 (installed February 21, 2026) with Textastic 10.9.2.

Symptom:

Voice Control appears to be active and recognizing commands (as confirmed by testing in standard text fields like Notes), but no text is delivered to Textastic's terminal input field.

Root Cause Analysis:

The issue appears to stem from a conflict between the iPadOS Predictive Text / Composition Engine and how the terminal view handles input:

- When Voice Control processes speech, iPadOS inserts tentative (composition/draft) text into the input field.

- iPadOS then commits the final text, replacing the draft.

- The terminal view does not correctly handle this new two-phase input process, resulting in no visible text being delivered.

Steps to Reproduce:

1. Enable Voice Control via Settings > Accessibility > Voice Control.

2. Open Textastic and launch a terminal session (e.g., via SSH).

3. Use a voice command to dictate a terminal command.

4. Observe that text does not appear in the terminal input field despite Voice Control confirming recognition.

Expected Behavior:

Dictated text and Voice Control aliases should be inserted cleanly into the terminal input field, identical to how they work in Textastic's code editor and other standard text fields (e.g., Notes, Safari address bar).

Impact:

This bug renders Textastic's terminal view completely inaccessible for users who rely on Voice Control for hands-free operation.

Additional Notes:

- Standard text fields, including Textastic's own code editor, handle Voice Control input correctly, confirming the issue is specific to the terminal view's interaction with the iPadOS composition engine.

- The issue did not exist prior to the iPadOS update that introduced the behavior on or around January 25, 2026.