Deactivate workflows & agents in self-hosted

💬 Workflows
1
  1. My goal: fully deactivate workflows and agents feature. Shouldn't be shown in UI menu.
  2. Issue: We have self-hosted defployed without workflow worker and code-executor, but the menu items are still shown in the UI.
2

I would also like to see if there is a way to deactivate and hide agents at either the Retool instance level or at a space level. We are also self-hosted.

3

Hi @rafael_cx and @eric-cheng,

It looks like there is a feature flag for turning off Agents. The name for it is aiagentsenabledbyretool and once it is turned off then Agents will be hidden in the UI.

4

@rafael_cx I believe the feature flag had been hidden by default on your org but I added it/made it visible so you should be able to find and toggle it in settings.

@eric-cheng I wanted to double check with you on if you want the feature flag toggle to be visible on all instances. If I make the change to have it no longer be hidden then it will appear on all instances and need to be toggled in a space or instance if you want to have Agents appear.

5

Hi @Jack_T ,

Thank you for the update.

Currently, we can see Agents in the navigation of each space

  • Instance
    • Space 1 (Agent visible in nav)
    • Space 2 (Agent visible in nav)

Would it be possible to hide Agents in the navigation of Space 2 for example?

6

Hi @eric-cheng,

So there is a way to have different feature flag behavior at the Spaces level.

It does require some work in the code base to alter the DB and doesn't have an easy GUI control unfortunately :sweat:

-- take note of the id of the space(s) you want to target 
select id, name from organizations; 

-- replace <featureFlagName> with the flag you want to toggle and jot down the id returned
insert into experiments ("id","name","createdAt","updatedAt") values (DEFAULT,'<featureFlagName>',now(),now()) RETURNING id;

— replace <spaceId> with the id from the first query, <experimentId> with the id returned by the second, and <trueOrFalse> with the desired boolean value
insert into experiment_strategies ("id", "strategy", "targetId", "experimentId", "value", "createdAt", "updatedAt") values (DEFAULT, 'organization', <spaceId>, <experimentId>, to_json(<trueOrFalse>), now(), now());

" There is no in product way to serve a different feature flag per space currently, but we can split based on the experiment_strategies table with some DB surgery"

7

Hi @Jack_T ,

Thank you for the info.

We are ok for the time being with having Agents visible.

1 Like
8

Hi Jack, thanks for the help. Where would I find that feature flag? I haven’t found anything.

9

Hi @rafael_cx,

I believe the feature flag is hidden until someone from the Retool team enables it for an org. Let me switch it on for you.

Credit Exchange AG, correct? I just applied the flag, let me know if it appears under Settings in your org.

10

Hi @rafael_cx and @eric-cheng,

So two pieces of information I just got from the engineering team.

  1. The Feature Flag is not going to be usable for this use case. I was told this was for internal testing and thus the feature flag is 'hidden' in the settings and is only viewable in our internal testing environment. There are likely plans to make this available to external users but for the short term I was incorrect on believing that the feature flag would be viewable and able to be toggled.

  2. You can hide Agent and workflows in your instance in another way! If you remove the permissions for users to use workflows and/or to use Agents, then the banner will be hidden and they will not be accessible. In terms of using this at the Spaces level, you would just need to apply this for the users that are going to be operating in the Space where you want this hidden. Unfortunately it will hide these features for the non-permitted users in all Spaces.