Added GitHub issue and ClickUp task synchronization (lazy) to a fork #61
Replies: 1 comment 4 replies
-
|
I'd love to hear more about these types of integrations and how people use them! At the moment my stance on these is to defer them to agents; my hypothesis is that you should be able to tell an agent to synchronize your beans with your preferred issue tracking service, and it should be able to do this quite reliably, assuming the necessary MCPs/CLIs/skills are configured, but I haven't tested this hypothesis so far for the simple and boring reason that I don't use any external issue trackers in my projects. Generally speaking I would prefer to keep Beans focused and simple, but I'd be happy to explore a "subcommand plugin" style system where
This would allow people to explore extensions to Beans without the code having to live in the Beans repo and executable itself. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I’d be happy to contribute this back but it seems a bit contrary to the beans ethos. If you or your LLM want a working sample to chew on: https://github.com/toba/beans
One rough edge I see yet is Claude sometimes treats my prompt for subtasks as a blocking relation and other times as a child relation, which look pretty different in ClickUp.
Beta Was this translation helpful? Give feedback.
All reactions