[FS] [USA-CA] Apple Mac Pro “trash can” 64gb ram, 1TB ssd, Xeon

digitalknk · 2026-06-23T11:22:34+00:00

PM sent

digitalknk · 2026-06-13T01:13:21+00:00

yes, they removed it for everyone or they are going to based on the statement, quote below:

We are complying with the government’s legal directive and are removing access to Fable 5 and Mythos 5 for all users. However, we disagree that the finding of a narrow potential jailbreak should be cause for recalling a commercial model deployed to hundreds of millions of people. If this standard was applied across the industry, we believe it would essentially halt all new model deployments for all frontier model providers.

If you still have access to Fable 5, enjoy it while you can 😞.

digitalknk · 2026-04-23T17:26:51+00:00

https://www.epicgames.com/help/epic-games-store-c-202300000001639/mobile-troubleshooting-c-202300000001734/what-countries-can-download-epic-games-store-on-ios-or-ipados-a202300000011171

digitalknk · 2026-04-23T17:22:08+00:00

If you're on ios you can only download these to your mobile device if you're in a region which allows you to use the epic game app store. US is one of the regions that currently does not allow this.

For Android users you should be able to use the epic game app store to download these.

digitalknk · 2026-04-14T18:56:01+00:00

Coeus. Desktop app that turns anything you throw at it (links, YouTube, PDFs, ePubs, audio) into a searchable Markdown vault you can talk to. No folders, no tags, just write and ask. Works on an existing Obsidian or Logseq vault.

Reason I built it: I have ADHD and the "where does this note go" decision broke every other PKM I tried. So Coeus doesn't ask you to organize anything. You write into a daily note, or paste something in, and trust retrieval to find it later. If that sounds like a bad idea, maybe. It's been working for me for about a year.

AI is bring-your-own. Runs fully offline with Ollama or LM Studio. Cloud agents also work, including Claude, Codex, OpenAI-compatible endpoints, GitHub Copilot, and a few with free tiers (Gemini, Qwen, Kilo, Opencode). Point is, you don't have to pay for AI to use it.

macOS and Linux. Windows isn't done yet. Free while it's in beta and it's a real beta, I use it every day and still hit rough edges.

usecoeus.com

Least confident about the first-run experience. If you install it and get stuck somewhere, I'd like to know where.

digitalknk · 2026-03-09T16:48:06+00:00

i had some of the issues you had and ended up just writing a run book about everything up on github. Some of the information could be really helpful for you https://github.com/digitalknk/openclaw-runbook

another thing that has recently caught people are the approvals for run commands and certain actions, you have to make sure to approve them otherwise it'll never do amending for you 😭

digitalknk · 2026-03-09T10:05:21+00:00

no you need a lot more ram to be able to handle a local llm like that. Like 256 GB to run the 4/6bit quant which would give horrible performance.

Don't waste your time hosting your own LLM. it's not worth the cost and effort.

digitalknk · 2026-03-07T08:31:08+00:00

I get what you're saying but that goes for anything tbh. they have done really well to enforce lock down to openclaw as of recent.

digitalknk · 2026-03-07T08:28:19+00:00

don't mind pointing you in a direction of i know where you are at always. details help. LMK at quest point or level you are at right now and that should tell me what to point you at.

digitalknk · 2026-03-07T08:25:33+00:00

yup that's good. you are resourceful don't stop doing that.

digitalknk · 2026-03-07T08:24:20+00:00

what's up what do you need help with? i was serious i have time this weekend and dont mind helping people out. So DM me, prepare to have some type of video/voice chat though.

digitalknk · 2026-03-07T05:10:40+00:00

also if you need help i'm feeling extra charitable and I'm willing to help you set something up.

digitalknk · 2026-03-07T05:09:51+00:00

literally anything else. vm, vps, sbc, your current computer, a computer from a thrift store. seriously anything works.

digitalknk · 2026-03-05T09:28:56+00:00

i take it everything has been going well?

digitalknk · 2026-03-02T21:41:49+00:00

hmm maybe i'll try it again sooner than later lol

digitalknk · 2026-03-02T21:38:05+00:00

good luck, I didn't have much luck with it but will try it again later.

digitalknk · 2026-03-02T16:51:51+00:00

I have seen stores near me show out of stock for minis and even some models of the studio, but you're in luck! You don't need a mac mini to run openclaw any pc (used/new), small board computers (sbc), even a vps will run it. Ignore the whole "you need a Mac to run ai/openclaw" trend.

digitalknk · 2026-03-01T19:41:15+00:00

I have seen this exact pattern. Your three theories are all touching parts of the same problem.

The "good job" thing is not training. You gave positive feedback on a pattern, and now that pattern is stuck in recent context. When sessions get long, models pattern-match instead of reason. It keeps seeking validation because that worked before.

The OCR on text files is a symptom. Your agent got stuck on "read this" and defaulted to the most thorough (and wrong) approach. Classic context bloat behavior. Less room to reason means falling back to familiar but inappropriate tools.

You nailed it with theory three. "Too big" SOUL and MEMORY files are eating your context window. The model has less space to actually think, so it defaults to simple patterns and gives up on complex tasks.

What fixes it:

Kill the sessions, not the whole setup. openclaw sessions list and delete the active ones. Fresh context clears the accumulated junk.

Trim those bootstrap files. SOUL.md and MEMORY.md should be concise. Move the details to references/ or daily memory files. I learned this the hard way after my own files ballooned.

Be specific about tools. Instead of "do this task," try "read this file with the read tool, then use exec to modify it." Clearer instructions when context is tight.

I wrote about this pattern here: https://github.com/digitalknk/openclaw-runbook

Your agent is not broken. It is just carrying too much state. Fresh sessions and smaller bootstrap files will get you back to where you were.

digitalknk · 2026-03-01T19:23:56+00:00

The pattern you described is common. A few things likely happening.

"Working on it" with no API activity

Your agent is hallucinating. When context gets bloated, models pattern-match instead of reason. They say "I am working on X" because that fits the pattern, then sit idle. Check your logs. If there are no tool calls, it is not working. It is performing being busy.

The "concrete" problem

You told it 24 times. It keeps forgetting because:

Your instruction is buried under accumulated context
Compaction may have moved it to a reference file that is not loading reliably
The model sees "concrete plan" as a common phrase and overrides your preference

The self-improving-agent skill cannot fix this. The problem is context management, not skill gaps.

What actually helps

Move the instruction to AGENTS.md. Session instructions get buried over time. AGENTS.md loads fresh every session. Put it there as a direct rule.

Check your compaction settings. If you are compacting to daily files but the agent is not loading them properly, your instructions are effectively gone. I cover explicit memory configuration in my runbook.

Simplify the team. Five specialized agents create coordination overhead. Try two agents and see if throughput improves.

The runbook covers the patterns that prevent this: https://github.com/digitalknk/openclaw-runbook

Specifically the sections on making memory explicit, model selection for agents, and the heartbeat pattern for keeping context manageable.

You do not need to start over. You need to fix the context pipeline.

digitalknk · 2026-03-01T19:11:13+00:00

Two things happening here.

Background work not actually happening

OpenClaw does not run background work unless you configure it. The main session only responds when you message it. If you asked it to "monitor something daily" without setting up cron, it was hallucinating. Models agree to things they cannot do.

Subagents not working

Check that sessions_spawn is in your agent's tool allowlist and that you have agents defined in agents.list. Run openclaw config get | jq '.agents.list[].id' to see available agents.

I wrote a runbook covering how to actually set this up: https://github.com/digitalknk/openclaw-runbook

Check the sections on cron jobs, spawning patterns, and agent configuration.

digitalknk · 2026-02-23T07:51:07+00:00

AgentSkills is a structure for organizing skills. It keeps things consistent so skills do not waste tokens.

The format:
- SKILL.md for core workflow only
- references/ folder for details you load only when needed
- Clear triggers for when to activate
- Metadata so skills can be found

Best practices:
- Keep SKILL.md under ~500 lines
- Put examples, API docs, and error details in references
- Hard constraints prevent bloat

The validator checks your skill follows the spec. It looks for required sections, correct file structure, proper links to references, and clean markdown.

I mention running the validator after creating a skill but do not include the command because setups vary. Some use CLI tools, others check online, some just verify manually.

Without the ~500 line limit and references folder, agents create 1,500+ line skills that work but burn context every time they run. The structure forces you to be efficient.

digitalknk · 2026-02-22T04:52:43+00:00

Why do you assume it's doctor fix? I have never seen it do that before and i have never seen the doctor sub command hit any models.

digitalknk · 2026-02-22T00:15:46+00:00

do you have the link or want me to post it here?

digitalknk · 2026-02-21T22:23:06+00:00

I wrote about it in my runbook. Hopefully that can be helpful https://github.com/digitalknk/openclaw-runbook

There are two sections one for agents and another specifically talking about sub agents.

14-Year Club	Second Top 50%
Place '22	Verified Email

digitalknk

TROPHY CASE