{"slug": "i-cured-my-adhd-with-ai", "title": "I cured my adhd with ai.", "summary": "A developer built Qlog, a terminal-based AI tool designed to streamline project management and daily planning without the overhead of traditional productivity software. The tool integrates with Neovim for prompt input, uses file injection and command piping for efficient context building, and generates markdown technical documents and daily agendas from LLM conversations. Qlog aims to eliminate the friction of re-explaining projects to AI assistants and avoid locking users into proprietary ecosystems.", "body_md": "(not literally, did fix the developer kind tho)\n\nthe problem was i had too many projects.\n\nand i needed to manage my day properly and i didnt want to use\n\nobsidian or notion or any of the current tools because its just too much work\n\ni had to spend time outta my day to work into these systems and waste brain power on\n\njust planning. i didnt want to do that at all, also didnt work because forcing yourself to write down\n\na notion board is genuinly the hardest thing possible. i mean you spend like 40 hours just crafting your board\n\nyou would be larping productivity basically.\n\n(i used notion once for an internship about a week was just spent making the board\n\nwe didnt even use it because the planning was being done in like google docs and sheets\n\nand someone had to move all the plans to notion just to look productive, its not worth it)\n\nproductivity software should not be a bottleneck of productivity\n\nso i decided the best kind of productive software is the one that works with you not against you.\n\ni looked into what i was doing the time i was not programming. and i realized i was just spending my time\n\ntalking to gemini/claude about my projects and during these sessions i would come up with new ideas and features\n\nonce i got this i would go and update my planning docs.\n\nalso these tools would lock you into their echosystems pretty hard.\n\nobsidian being a markdown file only tool is something that i took inspiration from.\n\nit was a very ineffecient system. and the problem was i spent half my time\n\nre explaining to the llms about the project even in the same chat.\n\nthis also ruined my workflow. i basically live in the terminal. my entire workflow is around neovim and a bunch of terminal\n\ntools. the only reason i was leaving the terminal was to talk to llms which took me out of the workflow\n\nto combat this i tried using ollama and llama.cpp. self hosting was great, the lightweight models responded instantaneously\n\nbut ollama cli and llama.cpp cli were lacking of a good interface and a workflow.\n\nso i looked into tui wrappers of these projects. when i used them i noticed none of them were really treating themselves like\n\nterminal applications properly. they were trying to be gui applications in a terminal which defeats the whole purpose.\n\nso now the solution was clear. i needed:\n\nand so i came up with qlog, short for quick log.\n\nthe first thing i wanted to nail in qlog was the input system.\n\nlotta tui tools create these input fields which are janky they are not feature rich because honestly, a single team working on\n\na whole tui app cant put enough dedicated time into an input system alone as much as say neovim or emacs devs put into it. they will\n\nnot have the huge echosystem that comes with these other tools.\n\nso, i reffered to the old texts. when in doubt reffer to philosophy.\n\nand, we got to the unix philosophy. do one thing and one thing well.\n\nwhy write a scuffed input implementation when you can hand it off to your $editor\n\nthis let me write my prompts in the comfort of neovim with all my plugins and hand crafted config\n\nand honestly this is what i was expecting with the tui tools. they dont leverage the power of the terminal enough.\n\nthe next thing i wanted was a good way to build a prompt.\n\nso i added two key things that makes qlog infinitely powerful.\n\nfile injection and command piping.\n\nNext thing I wanted was\n\nAn agenda planner. once I had a conversation about a project, an llm would read the whole chat and write a good\n\ntechnical doc in markdown format so it was really portable(you could cat it or less and it would be nice)\n\nOnce I had all my project technical docs and progresses I could talk to the llm and it would plan out my day and\n\nproduce an Agenda doc. This agenda doc was also stored as a readme and you could access it with a cli command.\n\nYou could just drop the cli command into your zshrc or bashrc and you would get reminded of your agenda.\n\nand honestly by this time qlog stopped feeling like an ai app and more of a shell utility which is exaclty what\n\nyou would want a productivity tool to be, you want it to be invisible. the more time you are spending trying to think of productivtiy\n\nthat much time you are not being productive\n\nThe project has an MVP rn (ikik ironic that the project to fix my projects is unfinished)\n\nBut honestly, qLog could help me complete qLog. bootstrapping productivity.\n\nHere's the github for those who want to check it out:\n\n[https://github.com/PranavDesai-Git/qLog](https://github.com/PranavDesai-Git/qLog)", "url": "https://wpnews.pro/news/i-cured-my-adhd-with-ai", "canonical_source": "https://dev.to/prnv_dsi/i-cured-my-adhd-with-ai-1227", "published_at": "2026-05-28 04:52:29+00:00", "updated_at": "2026-05-28 04:53:10.037025+00:00", "lang": "en", "topics": ["ai-products", "ai-tools", "generative-ai", "large-language-models", "artificial-intelligence"], "entities": ["Gemini", "Claude", "Obsidian", "Notion", "Google Docs", "Google Sheets"], "alternates": {"html": "https://wpnews.pro/news/i-cured-my-adhd-with-ai", "markdown": "https://wpnews.pro/news/i-cured-my-adhd-with-ai.md", "text": "https://wpnews.pro/news/i-cured-my-adhd-with-ai.txt", "jsonld": "https://wpnews.pro/news/i-cured-my-adhd-with-ai.jsonld"}}