What it is
The assistant helps with the fiddly parts of project work: sorting new requests, turning a brief into a checklist, pulling tasks out of meeting notes. It drafts suggestions and a person decides. Nothing is created, changed, moved or sent until someone clicks to accept it, and the person who clicks needs the usual permission to make that change.
What it can do
- Suggest details for a request. On a new request, choose Suggest details and the assistant proposes things like labels, priority and who might pick it up. Projects can also do this automatically as requests arrive.
- Plan this. Turn a task’s brief into a checklist of steps you can edit before adding.
- Meeting notes to tasks. Paste your notes and get a list of suggested tasks. Tick the ones you want.
- Describe an automation in plain words. Say what should happen (“when a task is approved, tell the client”) and get a draft automation to review before you switch it on.
- Caption help. Draft or tidy a caption for a channel. When a task has an image attached, the suggestions can take what’s in the picture into account.
It can also help you catch up, check and reply:
- Catch me up on a task. A short summary of a long task: what was asked, what has been decided in the comments and what is still open.
- My day. A plain run-through of what is due, what is waiting on you and what changed since you last looked, so you know where to start.
- Pre-flight review before approval. Before you approve, the assistant checks the work against the brief and the project’s brand rules and lists anything that looks missing or off. You still make the call.
- Status update drafts. A draft progress update for a project or task that you can edit and post yourself.
- Report narrative. A few sentences that put a report’s numbers into words. The figures themselves are worked out by Taskshire, not by the assistant.
- Ask for a filter in plain words. Type something like “overdue tasks for Sam with no reviewer” and get that filter set up for you to check and adjust.
- Reply drafts for client comments. A suggested reply to a client’s comment. Nothing is posted until you have read it and pressed send.
Some of these appear only where they are useful (for example, the pre-flight review shows on tasks waiting for approval), and your organisation may not have every one yet.
Every suggestion is shown to you first. Accept it, change it or dismiss it.
What is sent, and where
When you ask the assistant for something, Taskshire sends:
- what you asked about: that task’s title, brief and comments, the notes you pasted (and the image, for caption help), or, for things like a status update or report narrative, the tasks and figures of the one project you are looking at
- the names of your project’s labels, stages and members, so suggestions use ones that really exist
- your project’s tone and brand rules, if an admin has set them
That’s all. Work from other projects is never mixed in, and tasks you can’t see yourself are not sent. Your account’s email address and password are never part of a request. Anything written in the text you ask about is sent as it is, though, so don’t point the assistant at text that holds secrets.
Requests go to Anthropic’s Claude API, the service that powers the assistant. Each request carries an anonymous code in place of your name or email.
Taskshire keeps a usage log: who used which feature, when, and how big the request was. It does not keep what you asked or what the assistant answered. Owners and organisation admins can see the counts in organisation settings.
Switching it on or off
There are two switches, and both must be on.
- Organisation. An owner or organisation admin opens organisation settings, finds Assistant, and switches it on. It is off until someone does this. The daily limit is set here too.
- Project. Each project is on by default once the organisation is. A project admin can switch it off in project settings, under Assistant. This is also where to turn on Triage new requests automatically and to set the project’s tone and brand rules.
Switching it off stops new requests straight away. Suggestions already accepted stay as they are.
Limits
- Daily limit for the organisation. Admins choose how many requests the whole organisation can make in a day (200 unless changed, up to 5,000). It resets at midnight.
- A short pause for heavy use. One person can make about 20 requests in 10 minutes. After that the assistant asks you to wait a few minutes.
Requests that fail or are declined still count towards the daily limit.
What the messages mean
| Message | What it means |
|---|---|
| “The assistant isn’t set up on this server yet.” | Whoever runs your Taskshire server hasn’t connected it to Anthropic. Nothing can be sent until they do. |
| “The assistant is switched off for your organisation.” | An owner or admin needs to switch it on in organisation settings. |
| “The assistant is switched off for this project.” | A project admin has switched it off, or needs to switch it on, in project settings. |
| “Your organisation has used today’s … assistant requests.” | The daily limit has been reached. It resets at midnight, or an admin can raise it. |
| “That’s a lot of requests in a short time.” | You’ve hit the short pause. Try again in a few minutes. |
| “The assistant couldn’t help with that request.” | It declined to answer. Rewording usually helps. |
| “The assistant is busy right now” or “took too long to answer” | A temporary problem. Nothing was changed; try again in a moment. |
| “The assistant’s answer didn’t make sense, so nothing was changed.” | The reply couldn’t be used, so it was thrown away. Try again. |
Good to know
- The assistant only reads what you point it at. It can’t browse your project or act on its own.
- Text inside tasks and notes is treated as material to work on, never as instructions to the assistant.
- Suggestions can be wrong. Read them before you accept them.