Jump to content

Recommended Posts

- Say if you’re the author or submitting someone else’s workflow:

I'm the author

 

- Share a link to its main page: 

https://github.com/phguo/AskGPT

 

- Provide any data necessary for review, testing, and extra screenshots:

After it is installed, open a text editor, type "gpt write a poem for me" in Alfred

 

- If it has dependencies, say what those are unless they are explicit in the About or README:

See the README on its main page

 

- Provide screenshots, unless valid ones are in the About or README:

More can be found on its main page

alfred.png

v0.6_User_Configuration.png

Link to comment
Share on other sites

3 minutes ago, Rad said:

Hi @guoph, amazing work. Saw your post on Reddit

 

Question to the community: how can one be sure this is safe, ie no data is being sent anywhere apart to OpenAI?

 

Thanks!

Nothing is sent to anywhere other than OpenAI. To ensure this please follow the steps below.

  1. Download AskGPT.alfredworkflow from GitHub.
  2. Rename it as AskGPT.zip and then extract/unzip the file.
  3. You will find five files in the folder: two .png files, a .json file, and a .py file for your review. Additionally, there is a .plist file that can be viewed using PlistEdit Pro (https://www.fatcatsoftware.com/plisteditpro/).

Or

 

Once you have installed AskGPT.alfredworkflow, you can review the workflow process. The workflow simply passes your configurations and inputted content to gpt.py for further processing. While the gpt.py can be accessed by: right click on the icon of workflow -> Open in Finder.

 

This should clear your concern. Thanks!

Link to comment
Share on other sites

  • 1 month later...

@guoph There are typos in the configuration (and some in the code):

  • peaom → poem (in the screenshot).
  • temprature → temperature.
  • dubug → debug.

The Clear Keyword and Clipboard Keyword are quite confusing. When workflows have a Something Keyword in the configuration it means a keyword you type by itself, a user-configurable keyword, not an argument given to a keyword. It would be clearer if you made those into their own keywords or Alternative Actions.


A PYTHON_ENV won’t be understandable to most people. Python workflows should be usable with /usr/bin/python3, which is included in macOS.


Finally, the API_KEY also cannot be a Workflow Environment Variable. It’s the most important setting in the whole workflow. It has to be part of the regular configuration, preferably right at the top, and set as required. If you don’t set it a default value, it won’t be exported, you don’t have to worry about that.

Link to comment
Share on other sites

  • 3 weeks later...
On 5/12/2023 at 12:48 AM, vitor said:

@guoph There are typos in the configuration (and some in the code):

  • peaom → poem (in the screenshot).
  • temprature → temperature.
  • dubug → debug.

The Clear Keyword and Clipboard Keyword are quite confusing. When workflows have a Something Keyword in the configuration it means a keyword you type by itself, a user-configurable keyword, not an argument given to a keyword. It would be clearer if you made those into their own keywords or Alternative Actions.


A PYTHON_ENV won’t be understandable to most people. Python workflows should be usable with /usr/bin/python3, which is included in macOS.


Finally, the API_KEY also cannot be a Workflow Environment Variable. It’s the most important setting in the whole workflow. It has to be part of the regular configuration, preferably right at the top, and set as required. If you don’t set it a default value, it won’t be exported, you don’t have to worry about that.

Hi @vitor, thank you for your response!

 

If my Workflow relies on some Python packages to work. These packages need to be installed only before the first running of the Workflow. What is the best practice?

 

- Ask users to run `/usr/bin/pip3 install some_packages` in Terminal manually.

- Or are there other alternative ways?

 

Thanks!

Link to comment
Share on other sites

21 hours ago, guoph said:

If my Workflow relies on some Python packages to work. These packages need to be installed only before the first running of the Workflow. What is the best practice?

 

Package them with the workflow itself. To include a Python package with the workflow, use the --target option and set PYTHONPATH. StackOverflow has other options. Please make sure to install with /usr/bin/python3 so packages are built with the system python.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...