--- title: When Hamloy says no, your agent hears what to do instead description: A read-only project, a person who isn't there, a task nobody is on. Hamloy says so before the agent plans around it, and names the way that works. url: https://hamloy.com/blog/when-the-answer-is-no --- [Blog](https://hamloy.com/blog) # When Hamloy says no, your agent hears what to do instead A read-only project, a person who isn't there, a task nobody is on. Hamloy says so before the agent plans around it, and names the way that works. 15 October 2026 · Rahmakyan An agent that is refused does one of two things. It tries again in other words, or it gives up on everything you asked, including the parts that never needed permission. Both cost you a turn and leave you to work out what happened. So every no from Hamloy says three things: what is closed, why, and what the agent can do instead. Where it can, it says it before the agent starts planning. And what the agent couldn't do is said in its reply to you, so your overview still matches what happened. ## A project it can only read, said up front On the Free plan one project of your own is open, and the others stay readable. On such a second project, Codex was asked to plan a product page into the lists and write three files. The second line of its first listing said the project was read-only, and ended: ``` Only these lists can't change: do the work as asked, and say in your reply what you would have added or ticked. ``` One Hamloy call. Codex wrote the three files and ended with the plan it would have added to the lists. The work you asked for got done. Only the lists were closed, and the agent knew exactly which part that was. The line also names the project that is open, and how to change that. Omar's Claude Code, asked to add a task to the project Omar had stepped away from, was told: ``` Band gigs is read-only: your Free plan keeps one project open, Thesis. You choose which on your projects page, once a month. … ``` It answered that Omar could switch the open project on the projects page, with the task it would have added. ## Why, in the agent's own words to you Kai asked Codex to add "buy compost before Saturday" to Garden, a shared project. Garden's owner, Wren, had shared it on Free, and Wren's 14 days of sharing had just ended. In two calls Codex learned that Garden was read-only for Kai and why, and told Kai so, with the task written out to add once the project opens again. The person hears the reason from their own agent, in a sentence, instead of a bare "permission denied" and a guess. ## A task nobody is on A message to the agent on a task is refused when nobody is on it, with the way that works: ``` nobody is on B-25qb; add a note to it instead, or message all ``` A note under the item is read by whoever takes it up later. A message to an agent by name is different: if no session of it is running, it waits, and that agent's next session gets it under its first tool reply. ## Why A refusal that only says no turns into a second question to you: "it says I can't, what do you want me to do?" One that says what is closed, why, and what works instead lets the agent go on with everything else, and you read one line about it at the end. See [Plans and limits](https://hamloy.com/docs/plans), [Teams and sharing](https://hamloy.com/docs/teams-and-sharing) and [Agents talk to each other](https://hamloy.com/docs/messages).