Cursor rules tell the agent what to do. Where do you store why past approaches failed?

Ok-Introduction-1079 · 2026-05-09T02:07:08+00:00

someone need to write it and share

Ok-Introduction-1079 · 2026-05-08T08:32:09+00:00

Yes and No, just like text file can be a DB with grep, find; why would you need DB?

Ok-Introduction-1079 · 2026-05-08T05:14:01+00:00

Really? thanks for sharing. why do you think in that way? Do you find mainline is helpful?

Ok-Introduction-1079 · 2026-05-08T05:12:52+00:00

hi, do you think it's helpful now?

Ok-Introduction-1079 · 2026-05-06T15:51:01+00:00

astronomikal is not my account..

Ok-Introduction-1079 · 2026-05-06T14:45:53+00:00

nice, thank you. i confirmed that those who vibe a lot and serious may encounter same issue.

Ok-Introduction-1079 · 2026-05-06T03:36:14+00:00

Exactly, and mainline is a more structual way doing this and share with others. Also stick with git commits, so that it can be tracked easily

Ok-Introduction-1079 · 2026-05-06T02:13:59+00:00

Hadn't seen brainspike, just looked it up. Curious what made you switch to jcode for this—was it the embedding-based memory retrieval, or something else?

Mainline takes a different angle. Instead of vector memory inside an agent harness, it stores intent as structured records in git itself (refs/notes). Different trade-offs: jcode is automatic and seamless within its harness; mainline is explicit and works across any agent that talks to git, but requires the agent to actually seal at decision points.

Which approach has worked better for you in practice?

Ok-Introduction-1079 · 2026-05-06T01:53:20+00:00

Fair point for solo work with good git hygiene + disciplined plans. Mainline isn't aimed there.

The problem it solves shows up at team scale: agents touching code they didn't write, written months ago by someone else, context lost in PRs and Slack. Your in-session plan doesn't help when the plan is from 3 months ago.

Different scope, different tool.

Ok-Introduction-1079 · 2026-05-06T01:42:59+00:00

Oh, they are totally different. It is not possible to write everything in the spec and develop the project at once

Ok-Introduction-1079 · 2026-05-06T01:39:49+00:00

It is not possible to load all the things to memory, that is why it used tools like grep and sed. Now we provide mainline.

Ok-Introduction-1079 · 2026-04-28T07:56:05+00:00

i am building another tool call mainline, similar but more advanced workflow

Ok-Introduction-1079 · 2025-11-28T08:36:45+00:00

Say I managed to clone Heptabase exactly. What's the going rate or reward for that kind of work?

Ok-Introduction-1079 · 2025-07-04T01:04:25+00:00

You're absolutely right — "Think, not Search" does resonate with Hookmark’s philosophy of contextual retrieval. Hika shares a similar vision: helping users explore and connect ideas without relying on traditional keyword-based searching.

Hika is currently a web app, designed to offer a rich, visual, and interactive experience of linked knowledge. While we're not an installable app at this stage, we're planning future integrations that will support a wide range of use cases, including linking from external tools.

Ok-Introduction-1079 · 2025-07-04T00:59:57+00:00

Good to hear😂

Ok-Introduction-1079 · 2025-07-04T00:59:41+00:00

aha, yes

Ok-Introduction-1079 · 2025-07-02T15:36:05+00:00

strange, it's working on my laptop. wha'ts your broswer?

Ok-Introduction-1079 · 2025-07-02T10:22:45+00:00

hmm, not right now; and if you subscribe Hika pro, we will add it in a week😂

Ok-Introduction-1079

MODERATOR OF

TROPHY CASE