2n

Starting out

Begin by telling it what you're actually working on — not a clever prompt, the real situation, the way you'd brief a sharp new hire. The first day is mostly you talking and it listening; you're handing it the context it will keep. No setup ritual beyond that.

…more

Don't curate. Give it the messy version — the half-decisions, the things you're unsure about, the constraints you keep forgetting to mention. It does better with the truth of the work than with a tidy summary, and it won't drop the thread the way a fresh chat does.

Working with it day to day

Treat it less like a search box and more like someone who was in the room last time. You don't re-explain the project; you pick up where you left off — ask what you decided, hand it what you're stuck on, let it track several threads at once and keep you pointed at the one that matters when you drift.

…more

The habit that pays off is closing the loop out loud: tell it what you did, what changed, what you chose. That isn't admin — it's how the next conversation starts from where you really are, not from where you last bothered to write something down.

Turning dead time into work

The gaps in a day — between meetings, the ten minutes before a call — are usually wasted, because picking the work back up costs more than the gap is worth. With something that already holds the context, those gaps become usable: one question and you're back in.

…more

It's also where a lot of the quiet progress happens. Point it at a loose end before you step away, and you come back to a draft, a shortlist, a first pass — not finished work, but a running start, which is most of what dead time was costing you.

It starts to sound like you

After enough back-and-forth it stops guessing at how you'd put things and starts matching it — your defaults, your phrasing, the calls you tend to make. You notice it when a draft comes back needing fewer edits, then almost none.

…more

That isn't a personality setting. It's accumulation: it has seen how you actually decide across dozens of real situations, so its read on what you'd say keeps getting closer. The longer you work with it, the less translating you do.

How it adds up

None of this is dramatic on any given day. It's a little less re-explaining, a little less lost context, a few dead minutes made useful. The effect is in the accumulation: each week starts further along than the last, because nothing you built the week before got dropped.

…more

That's the whole idea, and it's quiet by design. You don't feel a system remembering; you feel the absence of starting over. Give it a month of real use and the difference shows up in the only place that counts — how little of your own work you're still carrying in your head.

Terms, plainly

The first 30 days are free — the full assistant, not a limited preview. You add your card when you start, but nothing is charged until after the 30-day trial. After the trial, 2n is a flat monthly subscription of $59 per instance, billed monthly. Each subscription is one dedicated instance on its own server, provisioned to you and never shared. Cancel anytime; billing stops at the end of the current period, with no termination fee.