It’s not perfect, and I appreciate those of you who tried out the original PMM-plugin (would appreciate the feedback from that). TLDR (AI summarised): Shipped the rewritten Poor Man’s Memory harness — now works across both Claude Code and opencode (Kimi K2.5, Gemini Pro/Flash) from the same project. Choose the model that fits the task, keep the memory. Tested in a multi-user Telegram channel holding concurrent 1:1 threaded conversations without cross-contamination. Previously validated switching between codebases mid-session. Link: github.com/NominexHQ/pmm-harness-dist Looking for early feedback and bug reports. Also built an agentic skill-porting suite between Claude Code and opencode as the first serious test of the rewrite. — The original plugin was Claude code only and worked well for me when I needed to switch beteeen code, CLI and Cowork (and between models) while retaining its memory. I tested it in a multi user environment (a telegram channel) and it held up holding multiple 1:1 individual threaded discussions with users a single group without straying. I had already been using it to switch between different codebases in a single session. So I had the suspicion it would hold up in such noisy environments. I just could test it until I implemented the telegram integration. This next one allows me to run my memory in opencode (where I run kimi-k2.5, Gemini pro and Gemini Flash) and Claude code from the same project. I get to choose which models or apps untike suits what I’m working on at any given moment. Would appreciate some early feedback and bug reports. I’ve been occupied rewriting Vera for opencode and realised I needed a plugin that allows me to analyse and port skills and plugins between the two. Writing the agentic suite for doing this was my first serious test of the rewritten PMM implementation.

You just saw how video production turns into code. Vote below, then tell us in the comments: what is one repetitive creative task in your work that could become a pipeline?

I've been in this community for about a month now and wanted to share where things stand with one of my builds. This isn't polished by any stretch. I do have a few other workflows like content-creator, document-creator, but I needed something to help me navigate my day-to-day as I begin a couple side quests outside my normal 9-5. The goal was simple: I didn't want another chat window I have to remember to open. I wanted something that knows my priorities, reads my calendar, checks my email, and texts me when I need a nudge. Not a chatbot, more like a Chief of Staff. And the goal is to operate within the bounds of the subscription with no extra costs, while also maximizing token efficiency. The other thing I didn't want to do is implement an orchestrating harness yet (OpenClaw, Hermes, etc). The challenge for myself was to keep this as simple as possible without inflating scope. Someone in this community said once: 'constraints are just as, if not more, important than your requirements. What do you NOT want your build to do?' I've definitely taken this to heart in my workflows. ## Planning I've made a few posts about this in comments, but I cannot stress the importance of planning before you build. My method was simple: - First I brain dumped context via voice dictation and transcribed this. Simple tools: VoiceMemos, copy, paste. - Next, I worked through the planning phase with the chat function of Claude in Opus 4.6. I wanted pushback, challenge, and for the model to force me to think deeper and keep me honest. This produced the product requirement document, or PRD. This was a multi-day process (a week?) in my free-time. - For the architecture build, I used Cowork. Handed it the PRD, answered a few basic questions, and then it went on it's way. Got it uploaded to a private git repo. - Currently, I'm working thru further debugging and walking thru the checklist within the PRD in a phased approach. As you'll see below, I have setup a remote screenshare so I can also let Cowork see what I'm doing. This was the most essential because we work TOGETHER to make things happen. it's like working side-by-side with my developer and engineer.