What changed after your comments

We launched here on Monday. The comments were less about the pitch and more about trust: how does this decide what my agent sees, and what happens to that decision when my code moves. So that is where the week went.

You can now mark the files and symbols that always matter, in secondos.yml or from the dashboard if you never open a terminal. The part worth caring about is what happens after that. Every sync re-checks each pin against the map it just built, and a pin pointing at a deleted path or a renamed symbol gets reported instead of quietly ignored. If a symbol was renamed, it looks through that file's own exports and asks whether buildGrap became buildGraph.

Then the ranking question, which is the one I expected to get. A pin only breaks a tie here. It cannot outrank a better match. We measured that on our own repo before turning it on: ten queries, three pins, two results moved by one position, top result never changed. Boosting the score was the easy version and it would have pushed correct answers down to promote a file somebody flagged last month for an unrelated reason.

Memory got the same treatment. It answered what happened, one event at a time, and that turned out not to be the question anyone had. There is now a diff that opens with the net move, plus three ways to find what you should delete: never recalled, low confidence, and stale since the code moved.

Smaller things off the same list. Memories can be edited and cleared. The projects page is a fleet view instead of fifteen stat cards. /scan/try shows you the output before it asks you for any work. And the login page stopped claiming a GitHub permission we never ask for.

Free tier is still real, local mode still needs no account, and the client is source available so you can read exactly what leaves your machine. Keep the questions coming, they are visibly setting the order.