AI Coding

As we dug deeper, however, a different problem emerged. No one on the team could explain why certain design decisions had been made, or how different parts of the system were supposed to work together. The code might have been messy, but the deeper issue was that the team’s shared understanding, the theory of the system, had quietly fragmented. They had also failed to write down or communicate the rationale behind decisions. They had accumulated cognitive and intent debt faster than technical debt, and it had paralyzed them.

Technical debt lives in your code. Cognitive debt lives in your head. Intent debt lives in the artifacts you never wrote - the goals, constraints and rationale that explain why the system is the way it is. It’s the one kind of debt your agents can’t pay down for you, and the one agentic engineering makes most expensive.

SymJack is a new attack technique targeting AI coding agents: a booby-trapped repository to trick your AI coding assistant into overwriting its own configuration through a disguised file copy, then run attacker code on the next restart. This is one technique that works against the whole category, don’t treat it as six separate bugs.

The era of fixed-fee AI spending just ended. If you’re a CTO or engineering leader and you haven’t noticed yet, you will very soon — probably around September 2026 when some budget alerts start firing.

it is clearly absurd for something like this to be used by anyone on their own computer to view local files. the goal of this project is to enable the viewing/navigating of files in browsers after exchanging over webrtc. i'm aiming for the experience to feel seamless for being able to navigate the folder structure on a remote device.

there are many browser-based office suites out there. this project aims to simplify the setup process by only using client-side resources; making it easy for users to get started.

https://ui.positive-intentions.com/iframe.html?globals=&args=&id=templates-filespage--native-real-folder&viewMode=story

unfortunately, it isnt open source, but i hope it helps to get feedback for improvements. in my project, the aim was to create an intuitive user experience for viewing files and folders in a browser.

A good way to test it out is to create a new empty folder on your computer and grant the webapp access to that folder. Note: the filesystem api provided by the browser will limit the access to explicitly approved folders. Some browsers also guard against access to important os directories on your computer and reject access automatically.

features:

• mounting local folders
• preview functionality for various filetypes
• browser based office suite
• basic folder management

upcoming:

• support for more filetypes
• better implmentation around browser-based office suite
• encryption-at-rest
• browser based file format conversions
• PWA

future:

when this project reaches a reasonable level of features and quality, I will be integrating this functionality into my P2P messaging app to build towards a "more" browser-based Next-Cloud-like solution. It would would be integrated into this app: https://enkrypted.chat/

IMPORTANT: Caution should always be used for all projects, especially like this. So I'd like to be clear that I am Al-slop-maxxing at scale. If youre looking for good code, clear docs or best-practices; you should look away now. While this is aiming to provide secure file-transfer and an intuitive office suite experience, I don't think it will ever be competitive against things like Next Cloud. It isnt audited or reviewed and i DO NOT want you to "trust me". I'd like to share for testing, feedback and demo purposes only. This is a technical demo of a unique concept. Feel free to reach out for clarity. Please use responsibly.