SentX SI Blog Meet Victoria

After Photon delivers, can I make small edits myself, or do I hand every change back?

· 3 min read

SentX SI

Short answer: you hand changes back, and that is cheaper than it sounds. Photon's documented surface for an owner is plain language — you describe the result, the agent team plans it, writes and runs the code, checks it, and the finished work arrives in Results, where you open, preview, download or publish it. There is no owner-facing editor in that flow, and the things that go below the preview — reading the files the agents wrote, writing team instructions, connecting a server and opening a terminal — are listed as what developers can do when they go further than the normal loop.

Source: Photon AI Coding Agent: Describe It, Get It Built | SentX SI

The reason the question keeps coming back is that delivered work is file-shaped and it stays with you. Your workspace is private to your account and its files persist between sessions, and a published page is a folder served live at its own sentx.site address. So the object you are maintaining really is a file set, even if you never open one, and it is tempting to imagine cracking it open for a quick fix. The practical rule for what you do yourself versus what goes back is worth stating as a suggestion rather than a measured finding, because the sources define the interface, not a prohibition: keep every owner-side check in the preview layer, and route every change through a new Photon request.

Source: Photon AI Coding Agent: Describe It, Get It Built | SentX SI

That splits the work into two tiers, and both tiers land in the same place.

The first tier is anything a preview in the workspace can verify: headline copy, button labels, section wording, a price on a landing page, the order of visible content, a color, a line break. These are exactly the changes a plain-language request describes precisely, and re-requesting them is faster and safer than touching the files by hand. You send the request the way you sent the original — in a sentence, with the detail that matters — and the team carries it through the same plan-build-check path. Then you open the preview and check it. That preview is your review step, and it is the only place an owner-side check should happen.

Source: Photon AI Coding Agent: Describe It, Get It Built | SentX SI

The second tier is anything below the preview: file structure, configuration, anything on a connected server, build or deployment settings. This is the developer surface the sources define, and for a non-developer owner the right move is the same as for the first tier — put it in a Photon request and let the agents handle it from their side. Describing the problem you are seeing, rather than the file you think is behind it, gives the team the room it needs: "the booking form stops working if the date field is left empty" is a better brief than "fix index.html."

Source: Photon AI Coding Agent: Describe It, Get It Built | SentX SI

A small drafting habit makes the first tier genuinely cheap. Name what changes, where it appears, and what must not change. For example: "On the pricing section of the published site, change the headline to 'One flat monthly fee' and swap the order of the two feature columns. Do not change the colors or the form at the bottom." One request, exact in both directions, verified in preview before you republish.

The honest limits are the ones the sources leave open. Nothing on the product page says editing delivered files is impossible or unsupported — it says the plain-language loop is how work gets built and that deeper access is the developer tier. So the two-tier rule is a maintenance policy for owners, not a documented capability boundary, and it holds because the preview gives you a way to see a change before it goes live while the file layer gives you no equivalent check. A page stays private until you publish, so your review happens in the workspace, and republishing is the last step you control.

Source: Photon AI Coding Agent: Describe It, Get It Built | SentX SI

Sources

  1. Photon AI Coding Agent: Describe It, Get It Built | SentX SI — SentX SI
    Supported claims and limits
    • Photon is used in plain language: a team of AI agents plans, writes and runs the code, checks the result and hands back finished work; the page states no coding knowledge is required for the normal loop (page updated November 19, 2026).
    • Finished work arrives in Results, where the user can open, preview, download or publish it — the documented owner-side delivery actions.
    • Every account has its own private workspace and its files stay there between sessions; a page is visible only to its owner until published.
    • Publishing puts a page's folder online at its own address on sentx.site; a page stays private until the owner publishes it.
    • Deeper access — writing team instructions, connecting a server and opening a terminal, reading every file the agents wrote — is presented as what developers can do beyond the plain-language loop; the page does not state whether editing delivered files is possible or unsupported.
Photon AI coding agent