Text of developer.amd.com › playbooks › github-slack-development-digest as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Build a GitHub-to-Slack Development Digest with Agent Canvas | AMD AI Playbooks

Skip to content Showing instructions for Platform: OS: Model: Qwen3.6-35B-A3B Recommended system memory: 64 GB 1h Advanced openhands agent-canvas automation github slack lemonade llm Lemonade 11.8 Node.js Latest Agent Canvas 1.10.0 Lemonade 11.7 Agent Canvas 1.10.0 Lemonade Latest Node.js Latest Agent Canvas Latest Lemonade Latest Agent Canvas Latest Lemonade Latest Node.js Latest Agent Canvas Latest Lemonade Latest Agent Canvas Latest Lemonade Latest Node.js Latest Agent Canvas Latest Lemonade Latest Agent Canvas Latest Lemonade Latest Node.js Latest Lemonade Latest Lemonade Latest Node.js Latest Lemonade Latest Lemonade Latest Node.js Latest Lemonade Latest Last validated: October 2026 View the Playbook on GitHub (opens in a new tab) Filters & more Platform Device Family Device OS Other Playbooks Automating Workflows with n8n and Local LLMs Generating Images with ComfyUI and Z Image Turbo Local LLM Coding with VSCode and Qwen3-Coder Running and Serving LLMs with LM Studio Running LLMs on PyTorch with AMD ROCm™ Software Build a GitHub-to-Slack Development Digest with Agent Canvas Building Custom GPU Kernels with PyTorch and AMD ROCm™ Building Your First Agent with GAIA Chatting with LLMs in Open WebUI Clustering Four Ryzen™ AI Halos with RCCL Clustering Four Ryzen™ AI Halos with RPC Clustering Two Ryzen™ AI Halos with RCCL Clustering Two Ryzen™ AI Halos with RPC Fine-Tuning LLMs with LLaMA Factory Fine-Tuning LLMs with PyTorch and AMD ROCm™ Software Fine-Tuning LLMs with Unsloth Getting Started with Lemonade Getting Started with Ollama Getting Started with OpenHands and a Local LLM Getting Started with vLLM Getting Started with Your Ryzen AI Halo (Project Zenith) Local Computer Vision with AMD Ryzen™ AI NPU Real-Time Speech-to-Speech Translation Remote Development with AMD Sync Running DeepSeek V4 Flash with ds4 Running Hermes Agent Locally with Lemonade Server Running OpenClaw Locally with Lemonade Server Requirements Model: Qwen3.6-35B-A3B Recommended system memory: 64 GB Details 1h Advanced openhands agent-canvas automation github slack lemonade llm Validation & Versions Lemonade 11.8 Node.js Latest Agent Canvas 1.10.0 Lemonade 11.7 Agent Canvas 1.10.0 Lemonade Latest Node.js Latest Agent Canvas Latest Lemonade Latest Agent Canvas Latest Lemonade Latest Node.js Latest Agent Canvas Latest Lemonade Latest Agent Canvas Latest Lemonade Latest Node.js Latest Agent Canvas Latest Lemonade Latest Agent Canvas Latest Lemonade Latest Node.js Latest Lemonade Latest Lemonade Latest Node.js Latest Lemonade Latest Lemonade Latest Node.js Latest Lemonade Latest Last validated: October 2026 Source View the Playbook on GitHub (opens in a new tab) Overview What You’ll Learn Core Concepts Setting the Memory Configuration Install AMD Software: Adrenalin Edition Advanced: Increasing GPU memory (Optional) Check for Software Updates Prerequisites Lemonade Node.js Lemonade Variables Used in This Playbook 1.

Start Lemonade Server 2. Verify the Local Model 3. Start Agent Canvas 4. Configure the Local LLM in the UI 5. Install GitHub and Slack MCP Servers GitHub MCP server Slack MCP server 6. Create the Digest Automation 7. Test the Automation Troubleshooting Next Steps Resources Device Family Processor OS Build a GitHub-to-Slack Development Digest with Agent Canvas Configure Agent Canvas, GitHub MCP, Slack MCP, and a scheduled OpenHands automation that posts a local-LLM digest.

Overview Developers spend a lot of time on small recurring loops: reviewing labeled pull requests, answering GitHub comments, triaging new issues, turning Slack threads into standup notes or incident follow-ups, and tracking release or research signals. Each loop is familiar, but it still requires judgment: gather the right context, decide what matters, and post a clear update where the team already works. OpenHands automations turn those loops into scheduled or event-triggered agent conversations: runs where an AI software agent can read context, call tools, and produce an update.

The shared automation templates in the OpenHands extensions catalog follow this pattern for GitHub pull request review, repository monitoring, Linear issue triage, incident retrospectives, Slack standup digests, and research briefs: an automation wakes up, uses configured integrations such as GitHub or Slack to fetch context, reasons over that context with a large language model (LLM), and writes back a result. Agent Canvas is the local control plane for building and testing those automations.

In this playbook it runs an OpenHands Agent Server, the backend process that executes agent conversations, and connects the agent to external services such as GitHub and Slack. To keep the workflow on your AMD system, the agent talks to a local model served by Lemonade Server. Lemonade exposes that model through an OpenAI-compatible API, so Agent Canvas can configure it like a remote OpenAI-style endpoint while the model, prompt, and workflow context stay local.

In this playbook, you will build one concrete automation: a scheduled GitHub-to-Slack development digest. It uses GitHub to inspect recent repository activity, Slack to post the digest, Agent Canvas API calls to configure and test the automation, and Lemonade to run the LLM locally. What You’ll Learn How to start Lemonade Server and verify a local model answers chat requests How to launch Agent Canvas and point its Agent Server at a local LLM How to install GitHub and Slack Model Context Protocol (MCP) servers through the Agent Server API How to create and dispatch a scheduled OpenHands automation that posts a development digest to Slack How to troubleshoot the most common local-model and automation failures Core Concepts Concept What it is Where it fits in this playbook Lemonade Server A local LLM serving platform built for AMD hardware that exposes an OpenAI-compatible API.

Your data never leaves your machine. Runs the model that powers the agent. OpenHands Agent Server The backend process that executes OpenHands agent conversations. Hosts the agent, its LLM profile, and its MCP servers. Agent Canvas The local control plane for OpenHands that runs Agent Server and a UI for inspecting agent runs. Launches the backends and provides the API you call. MCP server A Model Context Protocol server that gives an agent tools for an external service such as GitHub or Slack.

Lets the agent read GitHub and write to Slack. OpenHands automation A scheduled or event-triggered agent conversation that fetches context, reasons over it, and writes a result somewhere. The GitHub-to-Slack digest you build here. Setting the Memory Configuration Install AMD Software: Adrenalin Edition Download and install the latest AMD Software: Adrenalin Edition from amd.com/en/products/software/adrenalin.html . Terminal window if command -v rocminfo > /dev/null 2>&1 && rocminfo | grep -q gfx ; then echo "OK: GPU visible to ROCm" else echo "GPU not visible via rocminfo" >&2 exit 1 fi Advanced: Increasing GPU memory (Optional) You may need to increase the memory allocated to the GPU to run certain larger models or longer contexts.

These devices use unified memory — the GPU shares system RAM — so this means letting the GPU claim more of that shared pool. Leave roughly 20% of system RAM for the operating system. This step is optional; the default allocation is enough for most workloads. On Windows, adjust the memory in AMD Software: Adrenalin Edition : open it and navigate to Performance → Tuning → AMD Variable Graphics Memory . Set the value you need and reboot for the change to take effect.

Backup method (BIOS). If your system does not show the Variable Graphics Memory option in Adrenalin (some OEM systems hide it), set the UMA Frame Buffer Size in the system BIOS/UEFI instead: reboot, enter setup (usually Del , F2 , or Esc ), find UMA Frame Buffer Size — also labeled Integrated Graphics or dedicated GPU memory , often under Advanced or AMD CBS → NBIO Common Options — set it t

The rest of this page is on the live site.