Add Slackbot code

.gitignore

@@ -1,7 +1,174 @@
-*conf*.json
-.DS_Store
-__pycache__
-.idea/
+.idea
+pycache
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
 .env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# Visual Studio Code
+.vscode/
+
+# IntelliJ
+.idea/
+ml-models.iws
+ml-models.iml
+ml-models.ipr
+
+.DS_Store
+.databricks
+.gradio
+
+# Configuration files
+*conf*.json
+
+# Node.js / Next.js / Web development
+cookies.txt
+node_modules
+.pnp
+.pnp.js
+coverage
+.next/
+out/
+*.pem
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.pnpm-debug.log*
 .env.local
-*.log
+.env.development.local
+.env.test.local
+.env.production.local
+.turbo
+.vercel
+.env*.local
+
+# Playwright testing
+/test-results/
+/playwright-report/
+/blob-report/
+/playwright/*
+tsconfig.tsbuildinfo

PR_DESCRIPTION.md

@@ -0,0 +1,78 @@
+# Add Slack Bot with Glean-like UX and OAuth Authentication
+
+## Overview
+
+This PR introduces a Slack bot that provides personalized, authenticated access to Databricks AI agents. The bot implements a Glean-like UX featuring ephemeral messages, sharing capabilities, and multi-user support.
+
+## Key Features
+
+- **Glean-like UX**: Bot responds privately to users via ephemeral messages, with options to share responses publicly or dismiss them
+- **OAuth Authentication**: Seamless Databricks OAuth flow with automatic response after authentication completes
+- **Multi-user Support**: Each user authenticates independently and receives personalized responses
+- **Thread-based Conversations**: All interactions happen in threads for clean channel organization
+- **Interactive Buttons**:
+  - "Post in thread" - Share private response publicly
+  - "Dismiss" - Remove ephemeral message
+  - "Generate my own answer" - Allow other users to get their own personalized responses
+- **Visual Feedback**: Eyes emoji reaction on message receipt, white checkmark when shared
+- **Auto-respond After Auth**: Bot stores pending messages and automatically responds after OAuth completes
+
+## Architecture
+
+The bot uses Socket Mode for development and consists of:
+
+- **app_socket.py**: Main Slack app with event handlers and button actions
+- **oauth_server.py**: OAuth callback handler running on port 8000
+- **handlers/**: Message processing and authentication logic
+- **state/**: In-memory state management (can be replaced with Redis/DynamoDB for production)
+- **client/**: Databricks API client for agent calls
+
+## User Flow
+
+1. User mentions bot: `@DatabricksBot hello`
+2. Bot reacts with 👀 emoji for immediate acknowledgment
+3. **First-time users**: Bot sends ephemeral OAuth prompt in thread
+4. **After OAuth or for returning users**: Bot sends "Working on it..." status message
+5. Bot sends ephemeral response with "Post in thread" and "Dismiss" buttons (visible only to requesting user)
+6. Bot posts public message with "Generate my own answer" button for other users
+7. When shared: Ephemeral message disappears, response posted publicly, ✅ reaction added to original message
+
+## Technical Highlights
+
+- **Ephemeral Messages**: Uses `chat_postEphemeral` for private responses
+- **Response URL Pattern**: Uses `respond(delete_original=True)` for dismissing ephemeral messages
+- **Event Deduplication**: Properly handles both `app_mention` and `message` events without duplication
+- **PKCE OAuth Flow**: Secure OAuth implementation with proper state management
+- **Conversation History**: Per-thread history for context-aware responses
+- **Regex Action Patterns**: Dynamic action_id matching for button interactions
+
+## Testing
+
+Run the bot locally:
+```bash
+cd slack-bot
+python app_socket.py
+```
+
+The bot will:
+- Connect to Slack via Socket Mode
+- Start OAuth callback server on port 8000
+- Log all events and interactions to console
+
+## Future Enhancements
+
+- Replace in-memory state storage with Redis/DynamoDB for production
+- Implement rate limiting and request validation
+- Add token encryption at rest
+- Horizontal scaling with HTTP mode and load balancer
+- Structured logging with correlation IDs
+- Metrics and monitoring
+
+## Related Documentation
+
+See `slack-bot/README.md` for:
+- Complete setup instructions
+- Slack app configuration
+- Environment variables
+- Development guide
+- Troubleshooting tips