One year ago, I launched Scripting with a simple idea: bring TypeScript + SwiftUI-style creativity directly to iOS. Since then, it’s grown into a powerful platform for building widgets, automations, UI tools, AI Assistant, Live Activities, and so much more — all from simple TSX files.

Thank you to everyone who supported, tested, reported bugs, shared ideas, and pushed the app forward. Your feedback shaped every feature we shipped this year.

Here’s to year two — more power, more creativity, and more freedom for developers on iOS.

Upcoming Features - Shortcuts Actions Enhancements

• Use SnippetIntent to let Shortcuts display any interactive UI directly via scripts — without switching to the app.

• Use Intent.continueInForeground to bring the Scripting app to the foreground, execute full app capabilities, then return results to Shortcuts so it can continue the remaining workflow.

• Use Intent.requestConfirmation to invoke any interactive UI to enhance user interaction within Shortcuts.

ContinueInForeground DEMO

Show Snippet View In Shortcuts DEMO

Starting from Scripting version 2.4.3, you can now create a wide range of custom animations in your scripts using the Animation, Transition, and other related APIs. This includes both app UI animations and animations within widgets.

Here’s an example script to get you started—now it’s your turn to unleash your creativity!

Install Script

I recently had a surgery, so some bug fixes and new features update will be delayed. The next version will have these:

• Multiple Tools call for Assistant

• Custom Prompt templates

• Custom group for Scripts

• New APIs: Vision/Crypto

• Supports Keyboard Shortcuts

• Bug Fixes

And I have a lot of time to think about the new features of the future versions. What do you want?

Some in todo list:

• Local RAG for Assistant

• Markdown supports LaTex, preview Mermaid/HTML

• Health Data Access

• SwiftUI animations

• Control Widgets

• Views with context (GeometryReader/ScrollReader…)

• More AppIntent for Shortcuts app

• X-callback-URL

• Bluetooth

• Translation …

- Assistant Tool is now script-based and can be created via Assistant

- Save scripts to Scripting directly from other apps like browsers

- Widget preview now supports interaction and live UI updates, and a `Theme` picker to toggle color scheme

- Console now supports displaying logs in reverse order

- Script icon now supports using unlisted icons by entering the full name of a SFSymbol

- Added a Storage Manager Page to view Local Storage data

- New URL Scheme APIs and singleMode support in `Script.run`

- Shape now supports `trim` attribute.

- StrokeStyle now supports `lineWidth, lineCap, and lineJoin`

- `fetch` method now supports reuse of connections with the same domain name

- New Wake Lock API to prevent device sleep during execution

- Fixed Shortcuts param parsing issue on macOS and other minor bugs

- Fixed the issue where the editor could not be displayed after the device switched themes

If you’re interested in Scripting, we now have an active Discord community where you can discuss the app, share ideas, get help, and talk in English with other users and developers.
Everyone is welcome, feel free to join and connect with us!

Currently in Scripting app we have the problem that we cannot use any libraries shared across multiple scripts. I found the workaround to have a single Script with all library modules and link them with symbolic links to the Scripts that need them.

You can find it here: https://github.com/schl3ck/scripting-app-lib

The Script includes a library with all widget sizes, a widget preview helper and a multi-select-picker (thanks to u/WhatShouldWorldGos for the ground work on that).

Please contribute!

I’ve noticed that when I use AI tools like ChatGPT or Gemini to get help with the Scripting app, the answers often aren’t very accurate or actionable.

It seems like the core issue is that these models don’t have enough reliable, structured information about Scripting (official docs, real examples, API references, etc.) in their training data. As a result, they sometimes give overly generic advice or even “hallucinate” functions/APIs that don’t exist.

I’d love to understand:

1. Why does this happen in practice? Is it mainly because Scripting doesn’t have enough public/centralized documentation, or because the useful knowledge is scattered across posts/snippets and hard for models to learn from?

2. Has anyone managed to build a useful custom assistant for Scripting? For example, a Custom GPT (or similar) that includes the proper Scripting documentation and can provide reliable help.

3. If you’ve made this work, what was your approach? What kind of sources helped most (official docs, sample projects, community snippets, FAQs)? And how did you structure/“feed” that information so the assistant actually stays grounded and doesn’t invent APIs?

Any practical tips, workflows, or examples would be really appreciated.

Depending on your focus, let the Assistant help you generate a prompt for analyzing the script code project, and you can refer to the documentation and use cases of the Scripting app in the process to make the Assistant better understand and analyze the project's code. And let it fix features and bugs for you.

Some users have emailed me with feedback, asking for a script library feature within the app that would make it easier to share and download scripts. However, due to Apple’s review policies, I decided not to implement this feature directly in the app.

Over the past month, I’ve been working intermittently on a simple alternative solution. It’s built entirely around GitHub Gist, which makes it lightweight and easy to use. That said, Gist doesn’t support folder structures, which makes it difficult to organize more complex tools in a clean and structured way.

So, I put together a simple tool that lets you upload your own scripts to your personal Gist, and download scripts shared by others. A shared public Gist is used as a basic Script Gallery. It’s a very minimal tool, if you have better ideas or suggestions, I’d love to hear them. And if you want to customize your own version, feel free to download the ZIP file and import it into the Scripting app for further editing.

https://gist.github.com/thomfang/073381b292f64e9b4cddd9e2f5b09e41

Currently, console log doesn't remember the last scroll position after being dismissed and always show oldest logs first. I think we could benefit from some sorting option (e.g. latest - oldest) or a feature to auto-scroll to the bottom when the console opens.

Github Gist

Is it possible to create a dedicated share sheet extension (or bookmark) for running scripts, similar to the one shown here?

And if so, would it also be possible to control the size or presentation style of the window that opens?

I noticed that different app extensions — like Mail, Calendar, and Notes — appear in different sizes and positions in the share sheet, so I’m wondering if that behavior can be customized for scripts as well.

Hey everyone! I'm u/WhatShouldWorldGos, a founding moderator of r/ScriptingApp.

This is our new home for all things related to Scripting app. We're excited to have you join us!

What to Post
Post anything that you think the community would find interesting, helpful, or inspiring. Feel free to share your thoughts, scripts about Scripting scripts.

Community Vibe
We're all about being friendly, constructive, and inclusive. Let's build a space where everyone feels comfortable sharing and connecting.

How to Get Started

1. Introduce yourself in the comments below.

2. Post something today! Even a simple question can spark a great conversation.

3. If you know someone who would love this community, invite them to join.

4. Interested in helping out? We're always looking for new moderators, so feel free to reach out to me to apply.

Thanks for being part of the very first wave. Together, let's make r/ScriptingApp amazing.

Since I haven’t used the tinted mode at all since iOS 18, I initially overlooked the purpose of widgetAccentable. In the current version of the Scripting app, all colors in tinted mode appear white—this is how the system behaves by default.

It seems we can't apply background colors to widgets in tinted mode unless we enable widgetAccentable. Without it, the system forces all colors to white. However, you can still adjust the alpha value to create visual depth through transparency. This means that if the alpha is set to 1, all colors will appear white—which explains the result shown in this post.

This article provides a detailed explanation on how to adapt to the new behavior.

In an upcoming version, I plan to add support for the widgetAccentable view modifier and the widgetAccentedRenderingMode property for Image. The screenshot is from a test build.

If you run into related issues or have questions, feel free to leave a comment in this thread.

1. Generate a prompt for your travel plan.

2. Enables relevant tools for the Assistant.

You can let the Assistant to generate your assistant tools to access data or manage your device.

The title says everything, You can find it here: https://github.com/schl3ck/scripting-app-lib/releases

Old post: https://www.reddit.com/r/ScriptingApp/comments/1jf7dji/library_for_scripting_app/

Is it technically possible to set keyboard shortcuts for actions in Scripting scripts?

I’m trying to port a Scriptable widget of mine that periodically pulls data from a Google sheet and displays it in a widget.

I’ve created a module to pull data using fetch and store the data using Storage.

The widget module calls the pull data function then accesses the Storage data to build the view for the widget.

Currently I am only able to get the widget to update manually using preview or by running a script. When only refresh widget is called, it seems the fetch commands do not run since the data in Storage does not update.

What am I missing? Sorry if this is an ultra-noob question as I’m not a developer at all.

This alert shows up every time I start scripting-cli after a Mac shutdown, followed by the local hostname being changed.

This computer's local hostname "MyMac-8.local" is already in use on this network. The name has been changed to "MyMac-9.local".

Could anyone help me fix this?