Do we have a way to get info from notion into OpenHands? @gentle-apple-32922 maybe you have tried this? Right now I download markdown and upload to OpenHands, which is inconvenient

I want to add a description to this channel We have #C0A6U0HTD7X but this one is specifically for like MCPs, slack, linear, etc. style integrations, right?

set the channel description: Discuss how OpenHands can work with Slack, Linear, Jira, etc.

set the channel description: Discuss OpenHands Integrations with Slack, Linear, Jira, etc.

Something is up. When I try to

@ OpenHands

on github i only have one option of

@openhands-agent

but that doesn't work anymore I noticed Juan is able to

@ openhands

in a way I can't. Does it have something to do with my GitHub settings thinky spin OpenHands has access to ALL my repos not a select amount.

Hello team, please help me complete the PR.

Hi team - PR ready for review: https://github.com/OpenHands/OpenHands-CLI/pull/581 Adds a Tab navigation hint to the CLI footer (fixes #512).

I first thought I found a bug, but... I think it's a feature 😅 • if you start a Slack conversation, then send follow-ups from Web UI, it behaves as usual • but when I sent a follow-up from the Slack thread, it created a new conversation, new ID, and: ◦ FE shows no history; neither does public share ◦ but the agent got the history ◦ the runtime is different, it doesn't get new uncommitted changes ◦ the new conversations don't cross-post • in other words, it behaves like a 'fork conversation' for every follow-up from Slack • sure looks like a feature to me! 😂 💃

^ https://github.com/OpenHands/OpenHands/pull/13411 - fix for follow up messages not working in slack integration @limited-student-10747 The bug should have been caught, putting in a long term by addressing https://github.com/OpenHands/OpenHands/issues/13412

this dynamic slack loader is way better! good work team

looks like follow up messages are broken though 😞

How does the GitHub

@openhands

or the

openhands

label work? I met with @hundreds-twilight-32833 and realized I didn't know where it was in our docs.

slack integration easter egg: somehow the summary message got auto-translated into Japanese for me: https://openhands-ai.slack.com/archives/C09MTM3QPLG/p1773884944400619?thread_ts=1773774937.621939&cid=C09MTM3QPLG

I know we're working on the slack flow but this was a weird message. I think OpenHands was confused with our followup prompt

Speaking of the other integrations (github) and the summary message, this is how GitHub response looks like today*. Like, it just duplicates comments; unlike Slack, the agent has the gh token thus ability to respond by itself - and it does. So the summary seems superfluous*

I still have to consistently wait for the repo selector to time out two times every time I call the slack bot, which results in me waiting for about 30 seconds, it’s a bit frustrating. Any way I could get it so I can select “no repository” immediately @quick-window-91705?

Slack still doesn’t love us 😭

H guys. Has anybody integrated bitbucket successfully locally? In the cloud it works. But locally when I try to add my bitbucket via the settings with tokens it keeps on saying

Invalid token. Please make sure it is a valid bitbucket token.

Luckily I still had a valid app password for I cannot create any new ones. In curl and in a MCP it works but not here. Has anybody experienced the same problem?

https://github.com/OpenHands/OpenHands/pull/13791 - always provide "no repo" button option for slack integration (for those who don't want to wait for repo list network requests) cc @limited-student-10747

slack integration not firing? https://github.com/OpenHands/software-agent-sdk/pull/3022#pullrequestreview-4238256842

^slack not firing for me too

Hey @wooden-umbrella-84098 do we have someone currently working on "recommended automations" in agent canvas? I know you had a prototype. I have thoughts about concrete implementation and could possibly vibe something later today or over the weekend if nobody is on it already (cc also @hundreds-twilight-32833 and @elegant-branch-54423) My basic idea: 1. Find an appropriate OSS MCP/API marketplace and either use or modify their data into a format that we can use. 2. Create several "recommended automations" that have (a) a prompt to the agent about what the automation should do, (b) an example implementation of the automation, possibly with holes/unfinished design decisions, (c) a list of required MCPs for the automation, linked to "1". 3. Create a UI that displays "1" on the MCP page (in popularity order), similar to the MCP marketplace we previously had. Clicking on an automation will open a UI to add an MCP. 4. Create a UI that displays "2" on the automations page (in popularity order), similar to your prototype. Clicking on this will lead you through a process of (a) adding all required MCPs, re-using the interface from "3", (b) launching a conversation with the agent according to the prompt in "2". The reason why I'd prefer this design is that "1" and "3" allow people to use MCPs without automations, but "2" and "4" can re-use all components of MCPs so that the additional lift is low. (OFC if someone is working on this already I'm happy to let other people do it!)

👋 Hello, team!

I'm a little confused by the status of Slack/GitHub “summary” message issue. AFAIK: • Public poll results on Slack summary were: ◦ we want to remove the summary ◦ send back the last agent message • Github was perceived similarly, it duplicates comments • there was a PR for it, but the PR author closed it and I think maybe it wasn’t a good solution • Xingyao made available the last agent message via REST iirc • recently I thought the agent didn’t return the summary anymore in some conversations in Slack • but… these days it does confused dog Are we removing the summary?

Where is MCP config stored in agent-canvas? My slack MCP randomly lost auth

https://github.com/OpenHands/OpenHands/pull/14832 Fix for when we see "not account exists" bc the resolver happens to post back a summary comment containing the trigger word (at-openhands) for starting a new resolver session

For visibility, some other fixes made that were approved by all hands bot https://github.com/OpenHands/OpenHands/pull/14833 - disable the repo selection UI once a selection has been made for slack resolver https://github.com/OpenHands/OpenHands/pull/14828 - use final agent message as opposed to a separate llm completion request for slack/github summaries

Out of curiosity, what is

openhands-development

account about? I saw this on Vasco’s github entry point, too, I think.

github.com/OpenHands/OpenHands/pull/14950 - support for shallow git clone