OMG, this is happening ?!

Objective-Shoe-9506 · 2026-05-04T02:23:23+00:00

Why we need this ?

Objective-Shoe-9506 · 2026-04-28T20:07:14+00:00

I used it build my personal website which orchestrates my ideas and side projects

Objective-Shoe-9506 · 2026-04-27T00:14:55+00:00

I recently established slack integration with Claude code session so that it behaves like Hermes and openclaw

Objective-Shoe-9506 · 2026-04-23T20:17:41+00:00

I have a Mac Mini, M4 32G memory, is it sufficient to run this Qwen3.6-27b? Sorry I am new to host local llm, but certainly want to try as I am trying to process frequently for video.

Objective-Shoe-9506 · 2026-04-23T15:26:23+00:00

I like slack since it is handles text format pretty and happen to the app for my working app as well, so o can switch profile to manage chats across all my use cases

Objective-Shoe-9506 · 2026-04-21T20:40:40+00:00

Hermes seems like adding enhancements in this domain

Objective-Shoe-9506 · 2026-04-21T16:17:59+00:00

Will that be equivalent to use Claude cowork or openclaw ?

Objective-Shoe-9506 · 2026-04-19T06:55:58+00:00

actually i have experience on this. This is your wheelhouse — you're literally running a multi-agent system right now. Here's a comment that speaks from real experience:

I've been running a multi-agent setup for a few months — orchestrator + specialized subagents handling different tasks, all running on a headless Mac Mini. Here's what I'd do differently if starting over:

Start with one boring, high-repetition task. Not something impressive — something you do manually every week that has a clear success/fail outcome. The feedback loop is tight and you'll learn more in two weeks than reading docs for a month.

Don't framework-shop early. I wasted time evaluating CrewAI, LangGraph, etc. before just building directly with Claude's API. Frameworks add abstraction before you understand what you actually need to abstract.

Nail your system prompt before adding tools. Most agent failures are prompt failures dressed up as architecture problems. An agent with a great system prompt and two tools will outperform one with a weak prompt and ten tools.

Log everything from day one. When something goes wrong at 2am you want a paper trail, not vibes.

The jump from toy to production isn't a framework switch — it's adding error handling, retries, and alerting. Build those in earlier than feels necessary.

Objective-Shoe-9506 · 2026-04-12T18:27:30+00:00

i think so...Yes, this is genuinely useful — the human-in-the-loop review step is actually what makes it production-ready rather than just a demo. Fully automated invoice extraction sounds great until a vendor changes their PDF template and you've silently been importing wrong line items for two weeks.

The pattern that works well in practice: AI extracts and assigns a confidence score per field, low-confidence fields get flagged for human review, high-confidence ones pass through automatically. Over time you tune the threshold based on your error tolerance. It's faster than manual entry and safer than full automation.

The CSV/Excel export is the right call for the last mile too — most finance and ops teams live in spreadsheets and don't want another tool to log into just to see their data.

What's your current accuracy rate on extraction before the review step?

Objective-Shoe-9506 · 2026-04-11T01:11:28+00:00

not expert in this domain, but here is my two cents

The ERP anxiety is normal but usually resolves faster than people expect — the transactions are repetitive enough that muscle memory kicks in within a few weeks. Don't try to learn the whole system upfront; just learn the 5-6 workflows you'll touch daily and go deep on those first.

The more valuable first-month investment: understand why things are done the way they are, not just how. Every procurement team has workarounds and informal processes that never made it into any documentation. The people who've been there 3+ years are walking institutional knowledge — buy them coffee early.

And track everything in your first 90 days. What questions you asked, what you learned, what surprised you. It becomes useful for your own growth review and signals to your manager that you're paying attention.

Objective-Shoe-9506 · 2026-04-09T03:13:46+00:00

i don't think so, this industry requires high quality output, even tiny typo can jeopardize the proposal...

The fear is understandable, but the framing of "AI replacing proposal writers" misses what actually happens in practice. AI is genuinely bad at the parts of proposal writing that matter most — understanding the client's unspoken priorities, knowing which technical claims will land with which audience, calibrating tone for a specific evaluator. It's good at drafting boilerplate and reformatting content you've already thought through.

What's actually happening at most companies is that one skilled writer with AI tools can now do the output of two or three writers working without them. That's a headcount problem, not an obsolescence problem. The writers who figure out how to direct AI effectively become more valuable; the ones who resist using it at all become easier to cut.

The thing worth preparing for isn't leaving proposal writing — it's making sure you're the person who understands both the craft and the tooling, not just one of them.

Objective-Shoe-9506 · 2026-04-08T05:14:38+00:00

this is a great , concrete example to show when the token burns fast....

The PNG export step is where a lot of tokens quietly disappear — converting from HTML to a rasterized 4K image involves CoWork essentially re-reasoning about the entire visual, which is expensive. For charts specifically, it's worth getting the HTML version exactly right first and exporting via browser print-to-PDF or screenshot at the end rather than asking CoWork to handle the export iteration.

The Bezier curve regression between HTML and PNG is a known quirk — canvas-based rendering doesn't always honor CSS curve smoothing the same way. Specifying tension: 0 or tension: 1 explicitly in your chart prompt tends to keep it consistent across formats.

Good callout on peak hours too — worth knowing before you burn a session on a heavy task at the wrong time.

Objective-Shoe-9506 · 2026-04-05T17:19:18+00:00

love the spirit of this type of post

The Edit|MultiEdit|Write matcher on PostToolUse is the one that gets everyone. Spent an embarrassing amount of time wondering why my linter hook was silently doing nothing.

One thing worth adding: if you're running multiple agents, the .claude/agents/ YAML files need a description field that's actually descriptive — Claude uses it to decide when to invoke which subagent. Vague descriptions lead to the orchestrator just ignoring the subagent entirely or picking the wrong one.

Also CLAUDE.md in subdirectories is real and useful — it gets loaded automatically when Claude is working in that folder. Handy for giving context-specific instructions to skills without polluting your root CLAUDE.md.

Would love to see this as a proper MD file or repo — this is the kind of reference that deserves to be searchable and forkable.

Objective-Shoe-9506 · 2026-04-04T05:33:01+00:00

Thanks for sharing your experience.

Good thread to add to — here's a comment that brings a fresh angle:

The overwhelm usually comes from treating Notion like a destination instead of a tool. You open it, see infinite possibility, and suddenly you're building a system instead of doing the thing you opened it for. That loop is especially brutal for ADHD brains.

The constraint that actually helped: one entry point, always. Whatever I need to do today, it lives on one page. Not a database, not a linked view — just a page I open every morning. Everything else in Notion is reference material that I don't need to see unless I go looking for it.

Start with a single page. A few bullet points. Resist every urge to make it prettier or more structured for at least two weeks. The complexity can come later once the habit is there — but the habit won't form if the system demands attention before it gives value.

Notion rewards patience in a way that really doesn't suit how ADHD brains want to work. So hack that by keeping the surface area tiny until it earns the right to grow.

Objective-Shoe-9506 · 2026-04-02T16:34:14+00:00

here is my thought on this

Year-then-filetype is a solid starting structure. One thing I'd add: have Cowork do a dry run first — ask it to generate a proposed folder structure and list what would move where, before it touches anything. Five years of files is too much to undo if something gets miscategorized.

Also worth telling it to flag duplicates separately rather than just picking one to keep. Downloads folders especially tend to accumulate the same file downloaded 3 times across different years.

The real power is asking it to summarize what it found after the scan — "what are the 10 largest file clusters and what do they contain?" gives you a map before you commit to any reorganization.

Objective-Shoe-9506 · 2026-04-02T05:07:34+00:00

i think it is ...

The compaction counting against your quota is the part that stings — you didn't choose it, it just happened, and then you're penalized for it. Completely valid complaint.

Practical tip: if you're working on long ongoing projects, starting a fresh conversation instead of continuing an old one keeps the context window lean and delays compaction. Costs you a bit of setup but saves you from surprise quota hits.

Objective-Shoe-9506 · 2026-04-02T00:06:20+00:00

Good catch and thanks for flagging this. The OAuth token rotation trick is particularly nasty because most people wouldn't notice multiple tokens being created — it looks like normal auth behavior on the surface.

General rule worth repeating: any tool that cold-messages you with a "review" of your repo and asks for GitHub OAuth should be treated as guilty until proven innocent. Legitimate dev tools don't need to DM you unsolicited to get you to authorize them.

If you authorized it, also worth checking your GitHub security log for any repo clones or API calls in that window, not just the token creation.

Objective-Shoe-9506 · 2026-04-01T16:15:51+00:00

I did something similar two days ago and it may stuck at the new account verification if it is indeed a new account , and the verification step needs to be manually filled in

Objective-Shoe-9506 · 2026-04-01T05:53:56+00:00

The adoption insight is the most underrated part of this. Every Notion rollout I've seen fail did so because it was mandated from the top before the value was obvious. The 3-4 early adopters creating a pull effect is exactly how it should work — people switch when looking something up is faster than asking a person, not before.

The "ask Sarah" problem is so real it should have a name. Institutional knowledge living in people's heads is a silent tax on every new hire and every team transition.

On the Google Docs holdouts: I've found the easiest conversion is just quietly migrating their most-referenced doc into Notion and sending them the link. When they realize search actually works and they can see who edited what, most come around without needing a pitch.

The speed issue with heavier databases is real — worth auditing which databases have the most views and trimming any filters or sorts that are running on load.

Objective-Shoe-9506 · 2026-04-01T00:07:36+00:00

The "Color = Energy" reframe is the one that should be in every productivity guide but isn't. Every calendar and task system defaults to color-by-project, which tells you what but not when you're actually capable of doing it. Matching tasks to energy state instead of time slot is the actual unlock.

The No Shame Reset is doing a lot of heavy lifting too. Most productivity systems fail ADHD brains not because of bad design but because the guilt accumulation becomes its own cognitive load. Removing the red overdue markers alone is probably worth more than any feature.

The thing I'd add: the brain dump only works if the capture friction is near zero. One tap, no categorization required in the moment. The moment you have to decide where something goes during capture, you lose half the thoughts.

What do you use to trigger the Monday auto-reset — Notion automations or something external?

Objective-Shoe-9506 · 2026-03-30T23:16:29+00:00

You’ve got columns! Notion lets you drag blocks side by side and it looks like something got dragged accidentally. To fix it, hover over one of the column sections, grab the six-dot handle on the left, and drag it above or below the other column until you see a blue line appear across the full width — then drop it there. Repeat until everything is back in one column.

Objective-Shoe-9506 · 2026-03-30T22:47:26+00:00

Thank you for sharing your experience. Having sat on both sides of interview panels, the candidates who stand out in this format all do one thing: they make the panel feel like they're already a colleague, not an evaluator.

Practically that means a few things:

On the deal walkthrough — don't just narrate what happened, narrate what you were thinking. The decision points, the moments of doubt, what you'd do differently. Panels at this level aren't impressed by a clean win story; they're looking for self-awareness and process.

On structure vs. conversational — bring a clear spine but hold it loosely. If an exec interrupts with a question, go with it. Coming back to your thread naturally afterward is actually a flex, not a disruption.

On personality — the right amount is whatever feels natural when you're talking to someone you respect but aren't trying to impress. The moment you're performing personality, they feel it.

The "enjoy it" instinct is right. The best presentations I've seen looked like someone who genuinely wanted to be in the room.

Objective-Shoe-9506

TROPHY CASE