u/tanin47

We'd love to share an offline Cowork plugin for DOCX that we've built. It's more reliable, consumes much fewer tokens, and doesn't involve Cowork using bash commands/writing code.

We have been using it in-house for a few months now for legal work e.g. redlining NDA, adding comments, preparing the contract for the other party's counsel.

In the demo video, we show a simple workflow that we do regularly. What can be done further is to leave a comment on the doc and ask Cowork to address the comment. It's a seamless and natural of working.

I wonder if anyone would like to try it out. If you are a lawyer, that might be suitable. Feel free to drop me an email tanin(at)legalrabbit.ai if you are interested.

The plugin is here: https://github.com/LegalRabbit-AI/legalrabbit-docx-claude-plugin

I encountered a curious case of OOM where I have a piece of synchronous code that generates short-lived objects.

I was under the impression that, if the available memory is low, Node runtime will stop the code execution, perform GC, and switch back to the code execution. But that doesn't seem to be the case.

However, I failed to produce a simple code that reproduces this kind of OOM error.

I tried the below but it didn't cause OOM:

var arr = [1,2]

function main() {
    for (let i=0;i&lt;100000;i++) {
        arr = [3,4,i];
        for (let j=0;j&lt;100000;j++) {
            arr.push('' + j)
        }
        console.log('hello ' + i + ' ' + arr.length)
    }
}

main()
// run with node --max-old-space-size=10 test.js

I wonder if anyone has encountered this kind of OOM before and whether one has a reproducible code for this.

PS: I'm looking at other theories too but just want to ensure I understand this theory more in depth first.

We've built a Cowork plugin for DOCX. Great for legal work

Ruby vs. Java vs. TypeScript: my experience on building a Cowork DOCX plugin