{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaepvw6p6jkqjspedwfoppuhu4zjxmf5tdho2z2werdzvehovgaua",
    "uri": "at://did:plc:j4nmy4ymoeorm3j6hzbijapg/app.bsky.feed.post/3mgxjxgybstt2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreia6ahcnxajvxro3gdx3maylwngh44ulprbq2l6crs6beeeoihqmyy"
    },
    "mimeType": "image/jpeg",
    "size": 394460
  },
  "description": "The real change in AI may not be the models, but where they run. When AI enters the working environment, the workflow itself begins to shift.",
  "path": "/when-ai-moves-into-your-working-environment/",
  "publishedAt": "2026-03-13T18:24:20.000Z",
  "site": "https://hoeijmakers.net",
  "tags": [
    "Excel and the future cockpit of business logic"
  ],
  "textContent": "For most people, AI still lives in a chat window.\n\nYou open a browser tab, type a prompt, receive an answer, and copy the result somewhere else. It works surprisingly well, and for many tasks that model is perfectly sufficient.\n\nOver the past weeks I started experimenting with a slightly different setup.\n\nInstead of keeping AI in the browser, I began running several AI tools directly inside my working environment.\n\n## A different place for AI\n\nThe environment I am referring to is what developers call an **IDE** , short for  _Integrated Development Environment_.\n\nIn simple terms, it is a workspace where files, folders, editing tools, and terminal access come together in one application. Tools like Visual Studio Code are commonly used for this.\n\nTraditionally, IDEs are used to write and manage software. But in practice they are simply structured environments for working with collections of files.\n\nThat turns out to be an interesting place for AI to operate.\n\nThe IDE I used was Visual Studio Code.\n\n## From asking questions to working on material\n\nWhen AI runs in a browser, the interaction is mostly conversational. You ask something, receive a response, and decide what to do with it.\n\nWhen AI runs inside the working environment itself, the relationship changes slightly.\n\nThe AI is no longer separate from the material. It operates in the same environment where the files already live.\n\nNotes, drafts, document collections, code repositories, and folders are all directly visible within the workspace. The AI can analyse, summarise, or modify parts of that material with much less copying and pasting.\n\nIt starts to feel less like asking questions and more like working on the material together.\n\n## A small experiment\n\nIn my case the setup was simple.\n\nInside the IDE I opened several terminal sessions and ran different AI models as command-line tools. Each session could analyse files, summarise content, or help restructure information.\n\nThe interesting part was not the models themselves. The models are broadly similar to the ones people already use in chat interfaces.\n\nWhat changed was the **location** of the interaction.\n\nThe AI was no longer something I briefly consulted. It was part of the environment where the work itself was taking place.\n\n## Why this might matter\n\nThis setup is still somewhat experimental and more common among developers. But the underlying idea may turn out to be relevant for knowledge work more broadly.\n\nMuch of our work revolves around collections of material: notes, documents, drafts, datasets, and repositories of information.\n\nIf AI tools operate directly inside those environments rather than outside them, the workflow changes.\n\nLess asking.\nMore collaborating with the material itself.\n\nIt is a small shift, but it may turn out to be an important one.\n\n### Further reading\n\n  * Excel and the future cockpit of business logic\n\n",
  "title": "When AI Moves Into Your Working Environment",
  "updatedAt": "2026-05-10T08:53:36.945Z"
}