The Cohostly journal
Notes from the garden.
What we’re learning about running the small tools that agents build, and the people who share them.
rush hour, again.
Your agent built a tool. Now what?Most small tools die on someone’s laptop. Here’s the short path from “it works on my machine” to “my team uses it every day.”Read
wait for the light.
Why every app should ask before it actsApproval isn’t friction. It’s the reason people trust a tool enough to keep using it.found them.
Secret keys, explained without the jargonPasswords your app needs, kept hidden even from the people you share it with.a short nap.
Apps that rest when no one’s using themWhy your tools nap, and why you’ll never notice.room at the table.
How to share an AI-built app with your teamYou asked an assistant for a tool and it works. Here is how to get it in front of teammates without a server, a login system or a favour from engineering.moving in.
Host an app built with Claude or ChatGPT in one stepYour assistant wrote the code. The missing step is a place for it to live. This is what a good answer looks like, and what to avoid.every item ticked.
From vibe-coded prototype to something people rely on: a checklistEight questions to answer before a prototype becomes a tool your team depends on.this way.
What is an MCP server, and why would a host have one?A plain explanation of the Model Context Protocol, and what it changes when the thing on the other end is where your apps run.next, please.
Approvals for AI-generated changes: what to review and what to skipWhen an agent edits a shared app, the useful question is not “what is the diff” but “what could this change do?”all sent.
Connect Gmail and Google Sheets to an app without sharing a passwordApps need your accounts to be useful. They do not need your password, and they should not get more access than the job requires.made it myself.
Internal tools in the age of agents: why every team now builds its ownThe cost of a custom tool has collapsed. The cost of running it safely has not, and that is where the work moved.lights out.
How scale-to-zero hosting keeps small apps cheapAlways-on servers are priced for busy products. Small team tools are quiet most of the day, and hosting should reflect that.this one.
Where should you host an AI-built app? Five options comparedStatic hosts, app platforms, a rented server, a home machine and a host built for shared tools: what each is good at and where it breaks.on the list.
How to add login to an AI-built app (or skip it entirely)Building authentication is where assistant-written code is most likely to go wrong. Often the best login system is the one you do not write.filed away.
Where should an AI-built app store its data?Assistants love writing to a local file. That works until the app restarts, sleeps or moves. Here is where data should live instead.one step back.
Versions and rollbacks: how to change a shared app without fearThe ability to go back is what lets you move forward. A practical approach to updating tools other people rely on.say it clearly.
How to prompt an assistant for an app you can actually deployMost failed deployments start with a vague prompt. Here is a template that produces a project with a start command, a dependency list and no secrets in the code.covered.
A practical security checklist for AI-generated codeAssistants write working code, not necessarily safe code. Ten checks you can do without being a security engineer.a name on the door.
Put your shared app on your own domain: a beginner’s guideA branded address builds trust. Here is how custom domains work, the DNS records involved and the mistakes that delay them.right on time.
Scheduled jobs for small apps: weekly reports, reminders and clean-upsSome work has to happen whether or not anyone opens the app. How to run it on a schedule without leaving a server awake.lid on.
How to keep AI costs under control when your app calls a language modelA tool that calls a model on every click can cost more than its hosting. Limits, keys and caching that keep the bill predictable.back on the road.
Debugging a hosted app when you do not live in a terminalLogs, errors and a calm routine for figuring out why a shared tool stopped working, written for people who are not full-time engineers.