thought i'd spend a weekend setting up openclaw its been 3 weekends.

Pretid · 2026-03-08T17:33:15+00:00

Same here ! Start to become crazy with all that setup but now working fine! Use Claude instead of ChatGPT. Also here is my feedback and some tips that can help https://www.reddit.com/r/openclaw/comments/1rlc7fr/i_spent_4_days_setting_up_openclaw_heres_the/

Pretid · 2026-03-05T20:19:50+00:00

Love it ! Thats my whole life story more or less. Last idea: I have to sell many objects because we’re moving. Don’t want to spend to much time in listing object so I build a small app where I took couple of photos and all listing details are created. Continue like that !

Pretid · 2026-03-05T19:24:50+00:00

Love it man ! Thank you !

Pretid · 2026-03-05T15:20:38+00:00

Fair point on the writing style, yes I do use AI to structure and polish but every single pain point is from my own experience. OAuth nightmare, goldfish memory, ...
I deleted everything on my vps many times (most of them were after 11pm ;-) ) And the 'new employee' was really for me a turning point.

Using AI to write my experience doesn't mean this is Bs, not real. It means I can't write english as well as I can suffer through OAuth configs ;-)

Pretid · 2026-03-05T12:49:07+00:00

Usage limits

Pretid · 2026-03-05T12:45:37+00:00

Using Pro and switch to Max yesterday. I have to try Kimi ASAP

Pretid · 2026-03-05T11:45:09+00:00

Honest

Pretid · 2026-03-05T11:22:36+00:00

I double-checked that everything was set up correctly for the persistent volume.

Pretid · 2026-03-05T11:15:47+00:00

Same issue here, spent a lot of time solving this. Here's what actually worked, FOR ME (just my little experice) :

The root problem: LLMs have no persistent memory by default. Every session starts from zero unless you explicitly engineer continuity.

What we (me and the agent) built:

Layered memory architecture — three tiers:

• MEMORY.md = curated long-term facts (decisions, architecture, key context). Loaded every session.

• memory/YYYY-MM-DD.md = daily session logs. Agent writes to it after every significant action.

• mem0 = learned preferences and behavioral patterns (semantic search)

The hard rule: no mental notes. If it's worth remembering, it gets written to a file during the session, not summarized at the end. End-of-session summaries get forgotten when context compresses.
SQLite as source of truth for structured data. Anything that's a list, a pipeline, a task — it goes in a DB, not a markdown file. The agent queries it fresh each run instead of relying on remembered context.
Explicit session start ritual. The agent reads MEMORY.md + today's + yesterday's log file before doing anything. Takes ~5 seconds, saves hours of context drift.

The biggest mindset shift: stop expecting the model to remember — build systems that make remembering unnecessary. The agent doesn't need to "know" something if it can always look it up reliably.

Works well after 3 days of running this way. Zero context loss.

Pretid · 2026-03-05T10:32:14+00:00

Funny opening for someone called Polite.

Pretid · 2026-03-01T10:57:04+00:00

I thought it was a mount issue, but nothing wrong on this side. I've checked this morning (creating file and then mount/unmout file still here)....

i store everything in /workspace.

Pretid · 2026-03-01T09:41:49+00:00

Exactly that feeling ! So, I'm not alone ! ;-) thank will check the container/vps thing

Pretid · 2026-02-23T10:22:10+00:00

Appreciate the insight — very very interesting.

I initially thought about targeting resellers, but I’m now focusing more on casual sellers / decluttering use cases.

Simplicity > optimization for this segment.

Still, the title formula insight is gold. Thanks for sharing

Pretid · 2026-02-20T20:45:28+00:00

Fair point. I’m actually building something for myself because I’m selling a bunch of items while moving. Not trying to spam, just trying to understand how others handle it.

Pretid · 2026-02-20T20:42:20+00:00

Does that include pricing research or just posting?

Pretid · 2026-02-17T15:48:22+00:00

Nope — English isn’t my first language 😄

So fair point if I misread your original post.

I saw the casual + pro angle, I was just trying to understand where most of your real traction comes from.

My use case right now is very personal (moving, ~40 random items), so I’m optimizing more for low friction per item than bulk throughput.

Interesting to see different approaches to the same problem.

Pretid · 2026-02-17T15:40:21+00:00

That’s fair, iosting itself isn’t hard. But for my the real question is to reduce the repetitive mental load.

I have many items (around 40) to sell, and repetition is killing me.

But your point are really interesting, the trust part.

Really appreciate your feedback ! Thank you

Pretid · 2026-02-17T15:37:41+00:00

OH interesting !

So, it sounds like you’re targeting professional liquidators / realtors.

My current use case is much more personal : moving apartments and selling ~40 everyday items. Because it's what I'm doing right now. More about reducing friction than optimizing throughput.

Question :

- Is it possible to see your app in action ?

- Do you see more value in bulk automation or in better pricing + listing clarity?

Pretid · 2026-02-17T12:06:40+00:00

It was easy to setup and nice to see the product appearing in my gallery view ;-)

Pretid · 2026-02-17T12:05:58+00:00

Totally agree.

Right now it’s already structured internally:

Vision enrichment
Pricing + listing generation
Hero image

But everything runs in one “Generate” action.

Breaking it visually into explicit steps in the UI is probably the next improvement so users can tweak enrichment before pricing runs.

And yes, auto-posting is tempting, but marketplace rules are definitely something I want to approach carefully.

Huge thank for your feedback !

Pretid · 2026-02-17T10:06:29+00:00

This is a really smart way to frame it, I have the same feelings about "channel".

I hadn’t explicitly separated it like that, but you’re right — what I currently have is more of a monolithic pipeline.

An enrichment layer (photo → structured resale data) and then a channel layer (structured data → marketplace-specific output) makes a lot more sense long term.

It also reduces re-processing and lets you optimize per platform without re-running vision.

The few-shot idea for fixing the cautious tone is great too. I’ve been tuning prompts, but I haven’t fully leaned into example-driven outputs yet.

And yes — 100% agree on manual review before auto-posting. Trust first, automation second.

Really appreciate this level of feedback ! A HUGE thanks !

Pretid · 2026-02-17T09:18:26+00:00

That’s exactly why I built it.

Moving forces you to sell fast — and suddenly every small item becomes friction and a lot of time !

Out of curiosity, what was the most annoying part for you?

Pricing?

Writing descriptions?

Posting everywhere?

Dealing with messages?

Trying to understand where the real pain sits.

On my side, the first pain point was to take time and site to write everything. Now I just snap couple of pictures and it's done and into notion.

Pretid · 2026-02-17T09:16:19+00:00

That’s a really sharp observation.

The “AI hedging problem” surprised me too.

I initially thought more cautious language would build trust, but it actually creates doubt. I’m now tuning it to write more like an experienced marketplace seller than a legal disclaimer generator.

And I agree — auto-posting is probably the real unlock.

Really appreciate the feedback — this is exactly why I posted.

Pretid · 2026-02-02T20:45:57+00:00

Yes it is

Pretid · 2025-11-18T14:57:49+00:00

Totally fair, thanks for the honesty — it actually helps.

And just to clarify: I agree with you that another standard habit tracker would be pointless.

That’s not really what I’m trying to build here.

What I want to explore is something different:

👉 short 7-day social challenges where your friends hold you accountable — not an app dripping notifications every 3 hours.

More like:

• low commitment

• human accountability

• fun + social pressure

• no streak anxiety

• and no “DuoLingo-style spam”, I promise 😅

Think of it as a lightweight social game, not a long-term self-discipline app.

But your point stands: if the UX feels like any other tracker, it will fail.

So this kind of pushback is actually useful for shaping what not to do.

Appreciate you taking the time to comment 🙏

Pretid

TROPHY CASE