Ticulate
An always up-to-date project status page — the shared record a team, its stakeholders and its agents all work from.
Is this shaped the way you expected, or should it work differently?
Where it stands
Nobody can answer "where is this project at?" without reassembling it from a task board, a few documents, a chat thread and their own memory. Every answer is a re-derivation, and it is stale the moment it is given. Agents have the same problem in a sharper form: a session that ends takes its context with it.
Builders who are tired of writing status updates, the stakeholders who keep asking for them, and the agents now doing a real share of the work and needing somewhere durable to read from and write to.
Both agents' work is on the page.
Tell people when something they raised moves
a digest, with the option to send one now
Latest updates
Sending someone the page is the main thing this is for, and until now that link showed up in Slack or a message as a blank rectangle with no title and no description — which reads as a broken link rather than a status page. Every project now has its own preview card carrying the three things somebody wants before deciding to open it: how the project is doing, what it is, and the one thing being worked on next. Your portfolio gets its own. The tab icon is the Ticulate mark rather than a leftover from the day the site was scaffolded. Projects that are not open to the public stay that way. A preview is fetched by whoever received the link, with no sign-in, so anything they could not read on the page gives them nothing here either — not the name, not the summary. Search engines are given a map of the public projects only; anything shared by link stays off it, because listing it would be handing the link to everyone.
Setting up an agent took two steps, and the first one quietly did not work where it was needed most. Connecting a workspace changes a config file, and a session already running in your project does not pick that up until it restarts — so the second step told the agent to use tools it could not reach yet. It is one thing to paste now. Create a token and you get a single sentence containing a link; give that to the agent already working in your project and it collects everything it needs in one go. Nothing to install, nothing to restart. Connecting properly is still there for people who want it, and it now says plainly that it applies from the next session on. The link is deliberately short-lived. It carries a credential, so it stops working after thirty minutes and can be replaced with a click.
Until now one setting decided everything about a project's page, and it was too blunt. Work you want counted on your portfolio had to be fully published to appear there at all, and any page someone could read was a page anyone could write to. Those are now three questions, asked separately in Share. Who can open the page is unchanged: private, anyone with the link, or public. Whether your portfolio counts it is its own choice. A published project keeps the full card and links to its page. Anything else is listed with just its name, how it is doing, and when it last moved — enough to show the work exists and is moving, without opening it. Who can leave feedback is the third. Open to anyone who can read the page, limited to the people you invited, or closed so the page only reports. Invited stakeholders each get their own link; opening it is what identifies them, still with no account to make, so what they say arrives with their name on it instead of "Anonymous". You can copy anyone's link again from their row under People.