I have completed the initial research and analysis of the Tistory Auto Poster project. Here is a summary of the project's architecture and core functionality: ### **Project Overview** The Tistory Auto Poster is a comprehensive automation tool designed to generate and schedule blog posts for multiple Tistory accounts using AI (Gemini/Claude). ### **Core Components** 1. **Entry Points & Orchestration**: * `main.py`: The primary entry point providing CLI options for running the UI, scheduler, or single posts. * `run_with_sessions.py`: Orchestrates the integrated mode, managing Streamlit UI, background browser sessions, and the scheduler. 2. **Content & Image Generation (`core/`)**: * `content_generator.py`: Uses Gemini (or Claude CLI fallback) to generate SEO-optimized blog content based on keywords. It includes sophisticated logic for title/subtopic generation and HTML cleanup. * `image_generator.py`: Creates thumbnails and section images. It supports template-based generation (using Pillow) and AI-driven generation. 3. **Database & Persistence (`database/`)**: * Built with SQLAlchemy and SQLite (`tistory.db`). * Stores account credentials, keyword schedules, post history, application settings, and image templates. 4. **Web Automation (`selenium_bot/`)**: * Uses Selenium to automate the Tistory posting process. * `session_manager.py`: Maintains active browser sessions for different accounts to bypass repeated login hurdles and improve efficiency. * `browser.py` & `posting.py`: Handle low-level browser control and the actual Tistory editor interaction. 5. **User Interface (`ui/`)**: * A Streamlit-based web dashboard for managing accounts, keywords, settings, and monitoring the scheduler's status. ### **Key Features** * **Multi-Account Support**: Manage multiple Tistory blogs and Kakao accounts. * **AI-Powered SEO**: Content is generated with GEO (Generative Engine Optimization) in mind, using structured data like tables and FAQs. * **Automated Scheduling**: A background scheduler (`apscheduler`) checks for pending tasks every 60 seconds. * **Session Persistence**: Chrome profiles are used to keep users logged in, reducing automation friction. I am now ready to assist with any specific tasks, such as bug fixes, feature implementations, or architectural improvements. Please let me know how you would like to proceed.