OpenHands
Shanone’s OpenHands integration gives your agent 8 tools for driving OpenHands coding-agent conversations — creating, messaging, and monitoring autonomous coding sessions without leaving your Shanone workflow.Getting Started
1
Create an OpenHands API key
Generate a key from your OpenHands Cloud settings.
2
Add the key in Shanone
Go to Integrations in the Shanone dashboard, select OpenHands, and paste in the API key.
3
Retry your request
Once saved,
shanone_execute_tool calls for openhands_* tools will succeed.Available Tools
Shanone provides 8 tools for OpenHands, organized into these categories:Conversations
Conversations
openhands_list_conversations, openhands_get_conversation, openhands_create_conversation, openhands_start_conversation, openhands_stop_conversation, openhands_delete_conversationMessaging & events
Messaging & events
openhands_send_message, openhands_get_conversation_eventsCommon Use Cases
Delegate coding tasks
Create an OpenHands conversation, describe a bug or feature, and let it work autonomously
Progress monitoring
Poll
openhands_get_conversation_events to summarize what an agent has done so farMulti-agent handoff
Kick off several conversations for independent tasks and check on all of them from one place
Session cleanup
List stale conversations and stop or delete the ones that finished or stalled
Troubleshooting
openhands_create_conversation succeeds but the agent never starts working
openhands_create_conversation succeeds but the agent never starts working
Creating a conversation and starting it are separate steps — call
openhands_start_conversation afterward, or check the tool schema to see if it accepts a start flag directly.openhands_send_message doesn't seem to reach a stopped conversation
openhands_send_message doesn't seem to reach a stopped conversation
Messages can only be sent to an active conversation. Check its state with
openhands_get_conversation first, and restart it with openhands_start_conversation if it’s stopped.openhands_get_conversation_events response is very large
openhands_get_conversation_events response is very large
Long-running conversations accumulate many events (tool calls, file edits, terminal output). Request events incrementally rather than replaying the full history on every poll.