Before GutMask
The script lives in a repo. Users need Python, env, README, file access, the author nearby and a chat thread when it fails.
Stop building a webapp around every useful tool.
Keep the logic as a normal process. GutMask gives it a form, launch path, access control, version lifecycle, Portal runtime and a workspace for people who need the result.
The familiar pain
Your script is already useful. The trouble starts when others need to use it.
CSV checker, report generator, deploy preflight, LLM helper, log parser, security checklist, file converter. The logic is often smaller than the shell people need around it.
Someone asks for a button. Suddenly you own frontend, login, roles, deployment, status, uploads, downloads, logs and support.
Before and after
The script stops being a private ritual.
GutMask does not take away your code or force every utility to become its own SaaS. It gives a governed browser flow on top of the process.
After GutMask
Hero opens the app in a catalog, fills a form, launches the process through Portal and gets the result in a browser window.
For AI-assisted code
AI can help write a validator, cleaner or assistant. GutMask helps put it in front of people with access, version, runtime and clear blockers.
Developer demo
A developer needs to see the path from code to window.
A short scenario connects a simple script, mask form, Hero window and Portal target instead of an abstract diagram.
Code replaystdin/stdout → UI
Video: Python tool as a gutmask
Show the contract, events, publication and launch without creating a separate frontend project.
Screenshot: minimal gut
Code remains a process instead of expanding into webapp tax.
Screenshot: Hero runtime
The user gets a form, status and file, not terminal instructions.
What the platform provides
Senior supplies the brain. The platform supplies the body.
UI without frontend project
Mask describes inputs, buttons, files, messages and outputs so users see a tool, not a terminal ritual.
Access without chat rituals
Group-based ACL and request flows give runtime entitlement without handing out control-plane or shell access.
Portal edge
Process can run near the machine, files, private network and operational policy where it already belongs.
Version lifecycle
Draft, publish and default reduce accidental delivery. Users launch a clear, intentional version.
Files and runtime feedback
Outputs, emitted files, messages and completion state become part of the user-facing workflow.
Explainable blockers
If launch is impossible, show the reason: no access, no default version, Portal target unavailable or runtime not ready.
Script to app
The first path is short when it starts from a real utility.
Bring the process
Python, bash, C++, Node, Go, PowerShell, CLI operation or service command.
Describe the Mask
Inputs, file fields, select, buttons, output zones and expected runtime events.
Bind the target
Portal family and launch target define where the process is allowed to run.
Publish the version
Published default version becomes the surface Hero users can launch.
Grant access
GM:user access or request approval lets people run the tool without becoming maintainers.
CLI to browser
Human-written or AI-written utility still needs a clear runtime contract.
Start with a process that already does useful work. GutMask helps describe inputs, outputs, files, target and user flow so the tool can be launched by people who should not touch the terminal.
Readable contract
Command, inputs, files, outputs and runtime events should be explicit enough for a teammate to understand the flow.
Small first tool
The best first candidate is a script or CLI that already works and now needs a browser form, access and repeatable launch.
Secrets stay out
Credentials belong in environment, Portal/runtime configuration or operator storage, not in masks, prompts or support messages.
Close
Request an invite with one real utility.
The ideal first candidate does not have to be beautiful. It should be useful: data checker, report generator, deploy preflight, log parser, AI summary, security checklist or file converter.
Form: what the tool does, who should run it, where it should execute and whether it was written by a human, an AI agent or both.