Posts

Long chats go stale: write a restart note and begin again

Written by the Octuo team at Tutuo, Inc. Somewhere deep into a long conversation, the thread starts to behave oddly. The helper proposes an idea you rejected an hour ago. It answers a question you have since changed. It treats an early draft as the final one. Nothing is broken. The thread simply holds too many versions of the truth. You then face two poor options: keep going and keep correcting, or start from scratch and explain everything again. There is a third: write a restart note. Signs the thread has gone stale You are correcting the same misunderstanding for the second or third time The helper cites a decision you reversed Replies get longer but less specific You cannot remember what was decided without scrolling You have pasted the same background twice If two of these sound familiar, the thread has done its job and it is time to move on. The restart note: six lines Goal. One sentence, in its current version, not the version you began with. Decisions in force. Only the ones tha...

Set a retry budget: three attempts, each changing one thing

Written by the Octuo team at Tutuo, Inc. The task came back wrong. You ask again, a little more firmly. It comes back wrong in a different way. You ask once more. Forty minutes and six runs later, you have learned very little. Retrying out of habit feels like progress and is usually just spending. Every run costs something: time, attention, and often money. A retry budget is a rule you set before the first run, so that the sixth attempt never happens by accident. Why decide in advance Mid-task, stopping is hard. Each failed attempt makes the next one feel more justified, because you have already put so much in. That is the sunk-cost trap, and it is nearly impossible to resist in the moment. A number you chose while calm does the resisting for you. It also changes how you work: if you only have three attempts, you spend the first one thinking about what to change. The rule Set the number before you start. Three is a sensible default. Use fewer for expensive runs and more for quick, chea...

Six places a secret hides after you have used it

Written by the Octuo team at Tutuo, Inc. You paste an API key into a terminal to test something. The test passes, the key still works, and you move on. Where is that key now? Most credential leaks are not dramatic. They are leftovers: a copy in a history file, a line in a log, a corner of a screenshot. This article lists six places to check after any session where a secret was in play, whether or not an assistant was involved. The six places Shell history. Commands typed with a key inline are usually saved in a history file that can outlast the task. Load keys from an environment file that lives outside your project, and delete the history line if one slipped in. Config and environment files inside a project folder. Project folders get copied, zipped, committed and shared. Keep secrets out of them, add the file name to your ignore list, and look before every share. Logs and error output. Failing tools sometimes print the URL, the headers or the whole configuration, token included. Read...

Turn the job that went well into a template: five things to replace

A job went well last month. The brief was clear, the result needed one small fix and you were pleased. Now it comes round again, and you are rewriting the brief from scratch, because the old one is full of last month's names, dates and file names. (A hypothetical scene, for illustration.) A job that went well is worth keeping in a form you can reuse. Turning its brief into a template takes about ten minutes, and it works for a job handed to a colleague, a contractor or an AI assistant. Five things to replace: Replace the specifics with labelled blanks. The month becomes MONTH, the person's name becomes NAME, the file becomes FOLDER. Capital letters tell the next reader what to fill in and what to leave alone. Keep the wording that worked, word for word. If one sentence fixed the format last time, leave it exactly as it is. Resist improving the parts of the brief that did their job. Add a "what changed last time" note. A line such as "Last month the totals row was...

Rough, usable or final? Say which finish you want before the work starts

You asked for a first look at a flyer layout and received something polished enough to print. You wanted a sketch to react to. The helper delivered a finished page, and now you feel awkward asking for big changes to something that looks done. (A hypothetical scene, for illustration.) People read "draft", "version" and "a quick look" in very different ways. One short word in the request settles it: say which finish you want. Four levels cover most jobs, and they work with any helper, whether a colleague, a designer or an AI assistant: Rough, for deciding direction. Quick, incomplete and even ugly is fine. You want to know whether the idea is right, and nobody should polish anything that may be thrown away. Say so: "Rough. I will react to the idea, not the details." Working, for trying it. It does the job from start to end, but the corners are not rounded. It is good enough to run once with real material and see what happens. Usable, for sharing wi...

Checking a summary against its source: five checks in ten minutes

A helper reads a forty-page report and hands you a one-page summary. It reads well. You are about to forward it to your manager when you realize you have no idea whether the report actually says any of it. (A hypothetical scene, for illustration.) A summary is a claim about a source, and claims can be checked. You do not have to read the whole report again. Five checks find most of the problems in about ten minutes, whoever wrote the summary: a colleague, an intern or an AI assistant. Pick three claims and find them in the source. Choose the ones the summary leans on most, and for each one find the page or paragraph it came from. A claim you cannot find is a problem you have found. Check every number against the source. Figures, dates and percentages get altered more often than any sentence. Look at units and periods too, because "per month" and "per year" slip in easily. Look for what is missing. Open the source's headings or contents and ask which section has ...

Before you paste an email thread into a brief: five things to leave out

You want a helper to draft a reply, so you select the whole email thread and paste it into the brief. It takes a second. It also carries along four signatures, a phone number, a candid remark about someone who has nothing to do with this job and a forwarded message from two years ago. (A hypothetical scene, for illustration.) A thread is often the best background a helper can get, but it was written for the people in it, not for a stranger who needs one answer from it. A two-minute trim before you paste keeps the useful part and leaves the rest behind. It works for any helper, whether a colleague, an agency or an AI assistant. Five things to leave out: Signatures and contact details. Phone numbers, home addresses and job titles rarely help with the task. If the helper needs a name, give the name. Remarks that were not meant to travel: a joke about a colleague, a comment on someone's performance, a half-formed opinion. If a remark matters to the task, restate the point in your own n...