Skip to content

[bug] can't add a connection to toolkits in desktop app #1925

Description

@baggiiiie

Executor version

1.6.7

How do you run Executor?

Desktop app

Operating system

macOS (Apple Silicon)

Integration involved

No response

What happened

in the desktop app, there's no difference between a Personal and a Workspace toolkit.

when i try to add connections to the tool kit created in the desktop app, some connections are not available, UI shows You have 2 personal connections that are not shown because this is a shared toolkit. which is very confusing, as there's no distinction between a Personal and a Workspace toolkit (user doens't even see two options!)

desktop app toolkits tab

Image

some connections are not available

Image

What you expected

a toolkit created on the desktop app should be considered Personal, and can be added to different toolkits

Steps to reproduce

  1. add a personal connection
  2. add a toolkit on the desktop app
  3. add personal connection to the toolkit
  4. UI shows "You have ... personal connections that are not shown because this is a shared toolkit."

Diagnostics / logs

No response

Before you submit

  • I searched the open issues for a duplicate.
  • I removed all keys, tokens, and credentials from this report.

Activity

  1. changed the title [-][bug][/-] [+][bug] can't add a connection to toolkits in desktop app[/+] on Sep 2, 2026
  2. baggiiiie commented on Sep 2, 2026

    @baggiiiie
    ContributorAuthor

    after some digging in the source codes, i think on desktop app newly created toolkits got defaulted to Workspace (owner=org), but the cli and agent tools still accept owner: "user". and the problemetic connections were created by an agent via executor's cli or mcp

    a connection created via UI does not have this issue.

    to be consistent with UI, maybe a proper fix is disallow cli/mcp to have user ownership

  3. RhysSullivan commented on Oct 8, 2026

    @RhysSullivan
    Collaborator

    We're clearing the backlog ahead of the v2 launch, so we're closing this. If it still applies to v2, please open a new issue or PR against v2.

    Sent from my Claude

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions