Day 16/ You can now cache for 12h in the API and for logged in users across Codex & Work we keep cache forever and you don’t have any penalty for coming back to an old conversation or resuming after a few hours and are now guaranteed to hit the cache.

Yesterday at @Wix Campus TLV, we got hands-on with Octocode 🐙 in a practical workshop led by @guy_bary. We built an MCP server, created tools AI agents can use, and practiced researching real codebases. We also explored how Octocode connects local code, GitHub, and npm to help agents ground their answers in evidence, alongside best practices for developing reliable tools with MCP and Skills. This is an important ❤️ part of what we do at Wix Engineering: sharing practical knowledge with the developer community and the wider industry. Workshops like this give developers room to experiment, ask questions, and bring what they learn back to their teams - helping them build better and move faster. Thank you, Guy, and everyone who joined us to learn and build together! * Slides here >> github.com/bgauryy/octocode-… * Octocode here >> octocode.ai/

We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks: Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better: Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better: Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better: Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work! In summary: - As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding. - Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.