| |
| ▲ | jeroenhd 2 hours ago | parent | next [-] | | At work, I have my Claude set up to go through the issue tracker, source control, dashboards, team Slack channels, calendar appointments, and have it look for things like upcoming scheduling issues and deadlines that might get tough. A lot of those services need a corporate VPN or access to my local machine for the LLM to get the information right. Nothing I can't do myself (and generally I do keep an eye on that sort of thing), but it did catch a holiday for my foreign team members that seemed to have gone unnoticed, and remarked about a status mismatch between Jira and source control that made the dashboard misrepresent progress. It's not much, but it's an extra little check that works quite well. Another trick I'm experimenting with is having Claude rebase my open PRs waiting for review every day, and auto-solving conflicts when they arise. I don't trust it enough to let it push code to the repository, but I think I have the prompt set up in such a way that I might soon start using it. | | |
| ▲ | e12e 11 minutes ago | parent [-] | | While not trying to recreate the infamous dropbox comment - if you already have Claude code, are on Linux - can't Claude write a cronjob/systemd task that invokes itself for you? | | |
| ▲ | jeroenhd 2 minutes ago | parent [-] | | I could write a program that does this of course, but interpreting the current state of Slack threads is not something a Python script will be able to do without involving another LLM. I automated and script what I need or want to automate and script already, but for things like this where understanding of language is useful, I leave it to the slop machine. Things like "this is a holiday in country X but only for people living in province Y except for in town Z" are massive pain to script. Plus, if the issue tracker and source control automation were working correctly, I wouldn't need to read the status of both to get a good understanding of the situation. Any time scripting there should probably be spent (by someone else) on fixing the problem in the first place. When Claude eventually doubles or triples the token cost to stop hemorrhaging money, I'm going to lose these scripts and I won't be upset about it in the least. But until then, my "somewhat understanding of context" script-but-not-really setup is proving quite useful. |
|
| |
| ▲ | thewebguyd 2 hours ago | parent | prev | next [-] | | Cowork is pretty useful for non-technical folk for things you'd traditionally just write a quick little bash or python script for (which really, is what Cowork is doing behind the scenes anyway). I've gotten good results using it at work for keeping track of expense receipts. I dump them into an "Inbox" folder and Claude will OCR them, convert any images to PDF, rename, and move them into year/month/date folders and classify them (cost centers, based on a mapping and examples I gave it). This runs daily, checking the Inbox directory for new items. My next step is getting it to pull them from my email automatically for me as well, or from a specific alias so when I take a pic of a receipt on the go I can just email it and have Claude rename and organize it for me, then it all gets sent off to AP at the end of the month. Non technical knowledge workers have all kinds of little admin tasks like that which Cowork can do for them, where previously they lacked the skills or will to just learn some python and script it themselves. | |
| ▲ | baq 4 hours ago | parent | prev | next [-] | | I’d like the thing to read my mail twice a day and tell me if I missed something important. Haven’t set it up because I’m horrified by the thought of it reading my mail. Doubly so if it decides to do anything other than telling me if I missed something important. | |
| ▲ | Recursing 4 hours ago | parent | prev [-] | | Some good ideas here: https://posthog.com/blog/making-claude-cowork-actually-usefu... |
|
