Every piece of work waits for you in one Inbox
The Inbox is where the crew stops and asks. Articles, page fixes, pitches, questions and blocked runs land in one list, with the three decisions that matter most first. A new workspace starts in Draft: nothing is published, sent or spent until you approve it, and an approval left for 7 days closes having changed nothing.
7 days free · card required
DecisionIts AI visibility checker is the top-cited source for “free AI visibility checker” on Perplexity (3 of 3 answers). Attensira is not named in those answers yet. Pitch it, and who owns the relationship?
Choices: Answer · Snooze
Written for youChoices: Approve · Edit · Decline
- Connect GitHub so this run's page edit can ship as a pull request
- Blocked
- Install the crawler collector so we can see whether AI bots fetch our pages
- Steps · check
Every item is still waiting on our founder, which is the gate working and also why none of it has shipped yet.
Chief of staffattensira.com workspace, read over the Attensira MCP ·
Chief of staff · Ranks what reaches you, folds repeats into one row, and says what each run tried before it asks.
How does the Inbox decide what reaches you?
A row is one attempt; a decision is one thing for you to do. The Inbox turns many rows into a few decisions and ranks them the same way everywhere.
The crew stops where it must
In Draft, the default, everything that would leave the workspace waits here: an article, a page fix, a pitch, a spend. Anything that states a claim, such as a price, a number or a competitor's name, waits in every mode.
Each row asks one thing
Approve something we wrote, answer a fact only you have, or do something on your side, such as connecting GitHub or adding a DNS record. Notices that ask nothing are listed last.
Three decisions come first
Approvals about to expire, then what is at stake, then what cannot be undone, then quick questions. Seven runs blocked on the same connection are one decision: Connect GitHub · 7 waiting.
Then it is measured
Merged pull requests, placed pitches and delivered changes move to Done, each with its before-and-after re-read: Moved, Fell, No change or Too close to call.
What does an approval look like when nothing has run yet?
In Draft mode even a destructive step waits: the row says what it would do, and nothing happens until a person approves it. These two have waited on our own workspace since 15 September. In the product each row names the prompt by its ID; we show what it would do in words.
ApproveApprove: stop tracking one prompt and discard its historyWaiting since 15 Sep
This workspace is in draft mode, so nothing was done. Approve it here and it will run.
ApproveApprove: stop tracking a second prompt and discard its historyWaiting since 15 Sep
What can you do with a row?
What a row offers depends on what it is. None of it is hidden in a run transcript.
| An article or post | Approve it, edit the words and approve your version, or decline with a reason: Wrong, Not now, Already done or Never touch this page. |
|---|---|
| A rewritten passage | No Approve button, because we never publish a rewrite. Copy the new text into your editor, share a signed link with whoever owns the site, or ask your developer for access; then mark it shipped. |
| An approval from a paused run | Approve once or decline with a note. It is never edited, because your yes is bound to the exact call the run asked about. |
| A pull request | The chip shows its state read from GitHub: Open, Open · checks failing, Merged or Closed. Merge only happens when you press Merge, or a safe change when you switched on auto-merge. |
| A question | Type the answer or pick one offered. It is saved where every later run reads it, and the run that asked carries on. |
| Something to do on your side | Numbered steps with copy buttons. Where we can check the result, such as a DNS record or a line on a page, Done, verify it checks before the row closes. |
| Words for a page we cannot edit | New wording beside the passage as published, to copy into your CMS or forward by a signed link that expires in 30 days. Then Mark shipped with the live URL. |
What does the Inbox never do?
It is a control surface, not a task manager. Each limit is there so a yes always means someone read it.
- Silence is never consent: an approval left for 7 days expires, the run closes without the call, and a row says so.
- It never fixes a failing pull request. Attensira does not push a second time to a branch it opened, so a red build waits for a person.
- The keyboard shortcut approves only a single safe change whose effect can be undone. A claim, a spend or anything irreversible says Open it to approve.
- The agent cannot file a missing connection, a failed run or an expired approval itself. Those come from a call that really failed or a deadline that really passed.
- Merging is dashboard only. Neither the API nor an assistant over MCP can merge a pull request.
What happens after you approve?
The work goes where your site lives. Approve a page fix and, with GitHub connected, it opens as a pull request labelled attensira for your own review and merge.
Add a direct answer to /pricing: what each plan includes
attensira2 checks passed
content/pricing.mdx
- unchanged: # Pricing
- added: Every plan includes unlimited clients and invoices; plans differ in team seats and integrations.
Web engineer · Opened it on your yesExample · Ledgerly, a fictional brandWhat else do people ask about the Inbox?
Does Attensira publish without my approval?
What happens if I ignore an approval?
Which changes can go out without me?
Will a nightly failure fill my Inbox with rows?
Can I approve from my phone or my own assistant?
What does the Inbox cost?
Let the crew work. Approve what you like in one place.
7 days free · card required