What's new

v1.10

26 September 2026

• Documents get called by their name. No more "as we said in the CRM plan": every document is cited by its exact filename, so you can actually open it. The descriptive nickname comes after, if it adds anything. The trouble with a nickname isn't that it's informal, it's that it drifts between mentions until you can't even search for it.
• And if it's mentioned, it's in the index. Any document named in the estela also has to appear in the list of files that hold authority. If it isn't there, something is missing: either the document's entry or the correct spelling of its name.

v1.9

26 August 2026

• What you produce gets noted down there and then. Every file created in the project goes into the estela in the same reply, not "later". Before, a session could produce manuals, reports and decisions for two days and none of it reached the state file.
• It tells you if the estela has fallen behind. On opening it, it compares its date against the files in the folder: if there are newer things missing from it, you get told in one line before anything else. So you find out at the start, rather than three days later asking "where are we?".
• When tidying, numbers don't get orphaned. A conclusion and the figure behind it travel together: if the number goes, the claim goes with it. A conclusion without its source doesn't look broken — and that's the danger.
• When one project has become two, it says so. If tidying still doesn't make the file fit, the problem isn't space: it's two fronts living together. Estela proposes splitting them into two estelas instead of compressing further.

v1.8

19 August 2026

• Your older estelas catch up on their own. The ones created with earlier versions had no reminder in the header, and there was no way for them to get one. Now, the first time Estela opens one of them —even just to look something up— it adds it and carries on with what you asked for.
• Fixing and tidying stop travelling together. A small fix happens right away, without asking; tidying a file that has grown long is offered to you, and you decide. They used to be a single step, and that meant sometimes neither of them happened.
• Every project is set up from day one. When it creates the first estela in a folder, Estela notes in your CLAUDE.md that it should read it when starting. That is what makes it work without you having to remember anything.

v1.7

18 August 2026

• Your estela stops growing. Before, a long session left the file bigger: blocks of "done today" piled up and what mattered sank. Now the opposite happens — whatever you finish becomes a decision or closes an open item, and if the file has grown long it gets cleaned before anything new is written. A well-kept estela takes up the same room in September as it did in August.
• The first thing you read is still the first thing to do. The next action can no longer end up buried under new sections: the file has six fixed parts, and everything goes into one of them.
• A reminder inside the file itself. Every estela now carries a line in its header recalling how it is maintained. So if you open the file by hand, or another session touches it, the rules are in plain sight.

v1.6

16 August 2026

• Ask it which version it is. Estela now knows which version is installed and what changed in it. Just ask, in any conversation.

v1.5

16 August 2026

• Three checks before taking a fact as good. Never claim anything about a file without opening it, distrust whatever is asserted without a date, and check what a figure refers to before doing arithmetic with it. Estela used to stop a corrected error from coming back; now it also stops the ones trying to get in.
• The shareable view offers itself. The second time you ask for it in a project, Estela proposes keeping it up to date automatically. You decide.

v1.4

16 August 2026

• It is clear what each estela belongs to. It belongs to a project, and it outlives every conversation that touches it — it does not die when you close the chat. The earlier wording could suggest otherwise.

v1.3

10 August 2026

• A view that is never out of date. Say "keep the view up to date" and the shareable version of the status regenerates itself with every change: a file you can keep pinned in your browser that is never stale. Switched on and off per project.

v1.2

10 August 2026

• Estela introduces itself. The first time you use it in a project, it shows you right there what to say to create the status, see it, share it or close it. No manuals and no commands: you just talk.

v1.1

10 August 2026

• The dashboard adapts to what you have. A list, a board by date, or cards, depending on what tells your project best at that moment. And you can ask for a particular one: "dashboard in board mode".

v1.0

10 August 2026 · launch

The first public release:

• One status file per project that answers, in thirty seconds, what is decided, what is open and who it depends on, and what you parked on purpose.
• The table of corrected errors: every fact that was corrected stays there with its source, and Estela is forbidden from using it again. It is the section no summary has.
• Actions ⚡: the pending items the assistant can handle are left ready for you. Always as drafts — nothing goes out without your confirmation.
• Two ways to see it: an HTML file you can send to someone who does not use Claude, and a dashboard with buttons inside the app.
• It sets itself up: on first use it offers to leave everything ready so that each session reads the status without being asked.
• Validated with an internal test (100% correct with the skill against 52% without it) and used on real projects before release.