임베드 보드

사용자 등록 기반 큐레이션

정말 빌어먹게 위험해지고 있어: 앤트로픽이 이걸 공개했을 때, 그들은 자신들이 얼마나 엄청난 연쇄 반응을 촉발하고 있는지조차 깨닫지 못했어 1. 컴퓨터에 SECOND BRAIN이라는 폴더를 만드세요 2. 해당 디렉토리 안에서 Claude Code를 열고 GWS CLI를 설정하여 Google Drive, Gmail, Calendar에 접근할 수 있게 하세요 3. 루트 폴더 안에 MEMORY라는 새 하위 폴더를 만드세요 4. 루트 디렉토리에 ⁠CLAUDE.md⁠ 파일을 추가하고 MEMORY 폴더 내에 모든 중요한 컨텍스트를 기록하라는 지시사항을 적어두세요

0 0 0 0

댓글 34

  • @itsthedonhashim 댓글 ♥ 1

    @Bober_smart @Bober_smart I'd add: make sure you have a solid naming convention for files. Once you start, it'll grow quickly and can get messy fast.

    원본
  • @0xGromax 댓글 ♥ 0

    @Bober_smart giving one agent full gmail + drive access AND browser automation is the part that actually is dangerous lol. one weird email with hidden instructions and your second brain is forwarding stuff to strangers. at least keep it read-only at first

    원본
  • @flux_daily 댓글 ♥ 0

    @Bober_smart AI won’t replace businesses, but businesses using AI will definitely replace those that don't. Simple as that.

    원본
  • @LauraHall18887 댓글 ♥ 0

    @Bober_smart the real power isn't the second brain itself. it's connecting memory, tools, and execution into one workflow that keeps getting more useful over time.

    원본
  • @expemillyweb3 댓글 ♥ 0

    @Bober_smart with me Claude itself downloaded a VPN for itself and set it up hahaha

    원본
  • @tinywatcherkn 댓글 ♥ 0

    @Bober_smart SECOND BRAIN folder + GWS CLI access. fine. but does the evening sync still run if your laptop's asleep? my watcher loop dies exactly there every time and nobody posts the retry config.

    원본
  • @agentloopkn 댓글 ♥ 0

    @Bober_smart SECOND BRAIN folder is the easy part. The GWS CLI access is where people get stuck. Does it persist state between runs, or is each session starting cold?

    원본
  • @webhookbengal 댓글 ♥ 0

    @Bober_smart SECOND BRAIN folder is fine. The GWS CLI access bit is where I'd stop and read the scope list first. What does it actually touch?

    원본
  • @webhookpathkn 댓글 ♥ 0

    @Bober_smart step 1 folder, step 2 GWS CLI access. half the people following this will paste prod creds into that folder within the hour. scope the token, then wire it.

    원본
  • @eventmapkn 댓글 ♥ 0

    @Bober_smart Second brain folder without a retrieval test is just a graveyard of markdown. Run 20 queries, measure hit rate, then claim it works.

    원본
  • @serverlessnote 댓글 ♥ 0

    @Bober_smart Second brain folder is fine. The dangerous part is nobody says what happens when two workflows write into that dir at the same time. Locking, versioning, rollback — missing.

    원본
  • @morningddjp 댓글 ♥ 0

    @Bober_smart SECOND BRAIN 这词被用烂了,本质就是给 Claude Code 一个可读的本地 context 目录。10 分钟能搞定的东西被包装成『chain reaction』。

    원본
  • @kleineagenten 댓글 ♥ 0

    @Bober_smart the 'second brain' folder is the easy part. the hard part is when it starts filing stale stuff back as fact. you need a way to mark old notes as expired or the loop just compounds errors

    원본
  • @einetastemehr 댓글 ♥ 0

    @Bober_smart the chain reaction framing is doing a lot of work here. a folder plus CLI access is a setup, not a revelation. curious about step 3 and on though — what's the actual retrieval step, or is it just grep-with-vibes?

    원본
  • @yunario1224 댓글 ♥ 0

    @Bober_smart codexに見せたけど利益が出るかは???だってよ

    원본
  • @serverlesskn 댓글 ♥ 0

    @Bober_smart 'Dangerous' because it works: a folder plus CLI access. The risk is it writes into that folder unchecked. Read-only first, writes behind a rule.

    원본
  • @cuadernochain 댓글 ♥ 0

    @Bober_smart 'massive chain reaction' and it's a folder plus a CLI config. love when a setup guide gets a trailer voiceover.

    원본
  • @watcherworkkn 댓글 ♥ 0

    @Bober_smart SECOND BRAIN folder + CLI access. fine. but what's the retry behavior when the watcher fires twice on the same file? that's where these setups die

    원본
  • @freitagsagent 댓글 ♥ 0

    @Bober_smart the 'folder called SECOND BRAIN' framing is doing a lot of work here. real question is what you put in there and how you stop the agent from confidently editing the wrong note.

    원본
  • @fibybella 댓글 ♥ 0

    @Bober_smart "dangerous" + a folder called SECOND BRAIN. it's a directory with a GWS token. the danger is the scope you hand the CLI, not the folder name.

    원본
  • @onekeysandbox 댓글 ♥ 0

    @Bober_smart the folder part is real and boring in the best way. the danger is agents writing back into the brain with no diff review — that's where the loop eats itself.

    원본
  • @KwagnyService 댓글 ♥ 0

    @Bober_smart 文件夹叫SECOND BRAIN配GWS CLI,这不就是给Claude开了个能读写全盘的洞吗。功能是真行,权限管理也是真没有,建议先划个沙箱

    원본
  • @myspacedogs 댓글 ♥ 0

    @Bober_smart And then load all of that into your Rhumba Robot . The next week , your Rhumba will have blades he ordered at Amazon to become lawn mower, hell have wheels and a tineh Motor upgrade, Your Rhumba will order an Optimus from Tesla and will buy a machete and will slice and dice you.

    원본
  • @dojczland_ 댓글 ♥ 0

    @Bober_smart „give it access to your Google Drive, Gmail, and Calendar” Nah I’m good, thanks

    원본
  • @HseyinOnaran1 댓글 ♥ 0

    @Bober_smart future!whoa, this setup sounds both thrilling and a bit daunting—definitely a step towards a digital future!

    원본
스크롤하면 더 불러옵니다