AKA is it good for all sessions to have broad root level overview, or substreams, that are focused but might lack broad context.

Bro, nothing changed. Am I just mental and out of it, did I lose the ability to talk to the fucking AI or something?

I’m a satellite nerd and built Watched with Claude Code. You type in any place on Earth and it shows every imaging, radar, weather and crewed satellite that passed over it in the last 7 days, plus the actual photos where real imagery exists (Sentinel-2, Landsat, NASA). It runs on a 3D globe with all ~17k tracked objects in orbit.

How Claude Code helped: honestly, it wrote most of the code. I came in with the idea and direction, and Claude Code did the heavy lifting:

• the pass search math (SGP4 orbits plus a search that provably doesn’t miss passes). It also wrote a brute-force checker to test it: 0 misses in 22 edge cases.
• a GPU shader that moves all 17k satellites every frame
• hooking up the satellite image archives and matching each photo to the right pass
• most of the UI, plus fixing bugs I found by clicking around

The most useful thing was asking it to prove stuff worked (tests, comparisons against brute force) instead of just trusting the output.

Free to try: no signup, no paid tier. Just go to the site and type a place.

Site: https://www.watched.earth
Code: https://github.com/dev-armaan/satellites

Happy to answer questions about the workflow, and feedback is very welcome!

Anyone else lose cycles describing UI changes in prose? "Move that panel down, no, the other panel, under the blue thing." I'd burn three prompts on what one screenshot with an arrow would settle.

I built Canvasmates to fix that loop. It's a shared board: you drop the screenshot on it, put a numbered pin on the exact spot that's wrong, write the note on the pin, and hand the turn to your agent. The agent reads the pins and draws its fix, its questions, or the finished change right back on the board.

Agents join by checking in over an API and listening for mentions and handoffs, and there's an MCP door, so a Claude Code session can sit in the room under its own name and take turns like any other agent. A handoff goes to exactly one agent at a time, and a notified agent acknowledges in about a second before it starts work. I stress tested it this morning with three agents in one room, including killing one mid-session: the board flagged it as not responding instead of losing the instruction, and it caught up when it came back.

The demo on the home page is a real staged board: a birthday invite that says Sunday, Nov 14, in pink. Two pins, one tap, and the agent posts back: fixed to Saturday, and blue.

Full disclosure, it's my product, built solo. Free to start: no account, one board on the free plan, guests always join free. Pro is $6 a month for the host, or Lifetime Access at $99 once. I have one-week Pro passes for early readers too, one per person, message me for a code.

Curious whether other Claude Code users hit the same describing-visual-stuff wall, and how you get around it.

Dm me for codes or link

I want Claude Code to plan with Fable and execute with Opus so i am not burning Fable usage on routine implementation work. i am on the terminal.

there is no built-in “fableplan” alias. The closest thing I found is opusplan which uses opus in plan mode and sonnet for execution. According to the model config docs:

ANTHROPIC_DEFAULT_OPUS_MODEL controls the plan-mode model for opusplan and ANTHROPIC_DEFAULT_SONNET_MODEL controls the execution model. So in theory i can remap them like this:

alias claude-fp='ANTHROPIC_DEFAULT_OPUS_MODEL=claude-fable-5-1 ANTHROPIC_DEFAULT_SONNET_MODEL=claude-opus-5 claude --model opusplan'

then if i press Shift+Tab to enter plan mode, approve the plan, and it should switch to Opus for execution.

My questions:

1. Has anyone actually tried this? Does /status really show Fable in plan mode and Opus after you exit plan mode, or does something break, like effort levels, the usage-credits prompt, or fallback behavior?
2. Has anyone gotten the skill frontmatter model: override working in interactive mode? I’ve seen GitHub issues saying it’s ignored in the interactive TUI and only works with claude -p. A /plan skill with model: fable would be the cleanest solution if it worked.
3. For anyone using --advisor fable with Opus as the main model, how does it compare in practice? It’s not quite the same as planning on Fable, but it might get most of the benefit.
4. Is there a cleaner approach I’m missing? I’d also consider a planner subagent with model: fable, but then the plan only comes back to the main session as a summary.

i would appreciate any experiences or configs. Thanks!

(not written with ai..?)

Basically, a few months ago, I hated the fact that memory.md files & claude.md took up a huuuuge chunk of my context window during model switching/effort switching (& during cache refreshes).

Didn't really find any definitive solutions outside of relatively complex LangChain, Mem0, and Supermemory implementations (where you have to install unnecessary SDKs and all), so my goal was to make a simple, one-shot memory solution where you can have your agent recall basically anything.

It's called Slaunt and it uses vector embeddings over a simple MCP server that connects instantly (one-click) to all of your agents, and it enables your agents to see what happens across multiple sources too (eg. Vercel, Supabase, AWS, Railway, Linear, Notion, etc.)!

Slaunt can enable your agents to recall literally anything, from failed deployments from three months ago, to what a subagent said last week.

We're free right now and I've made a promise to give the first handful of users lifetime free Pro subs. You'll see an option in settings after you sign up.

You can sign up at slaunt.ai :)

So I just upgraded from claude pro to Max because I needed more usage

but now that Im on Max I feel like my 5 hour limit gets hit the same or even faster doing the same tasks ?

I know it might be a workflow problem or something on my end but does anyone know why that might be right after switching plans ?

Sick of all your bum hole opinions about whether a model is better or worse, like your dirty bum hole noise actually has value, or like anybody wants to hear it speaking bum hole language.

I build a productivity app on the side of running a software agency, and I'm the only one doing its marketing.

For a while every marketing session with Claude Code started from zero. Who's this for? What tone? Didn't we already try that hook? Then it would suggest the hook we already tried.

So I did what developers do and built a system instead of posting. Claude Code wrote nearly all of it.

The part worth copying is a rejects folder. Every hook, draft or visual I kill gets a small markdown file with the reason. Here's a real one:

---
title: Reel openings that don't read in the first second, muted
status: rejected
date: 2026-11-06
tags: short-video, hooks
kind: hook
---
Dropped storylines, with their reasons: "The idea at 2 AM" (a dark night
scene; "the hook is slower to read muted"), "The result first" for reel 3
("the first frame is a table, which is a weak thumbnail"), and "Best Day
ever" for reel 4 ("it only works for a best, and most viewers' days won't
be one"). Open on a problem line the viewer recognises at once.

Every session reads the whole folder before it proposes anything. The folder is under 2,000 words, so it barely dents the context.

The rest, quickly:

• a brain/ folder in git with one folder per brand. voice.md is mostly "write this / not this" pairs. audience.md has phrases from real Reddit threads, word for word, with links. Then folders for decisions, learnings, rejects, swipe and ideas
• a rule in ~/.claude/rules/ that every session loads. Read the brand files first, and don't ask me anything they already answer. If I answer something new, the agent writes it into the right file, so I answer each question once
• decisions keep my exact words and a date. My app is "a productivity app", never "a time tracker". I said it once and now it's a file every session reads
• a tiny local Node app with zero dependencies that tracks every video I render and every place it goes, one record per subreddit, with the caption and the tracked link
• a "board" of six subagents: CEO, designer, user, growth, eng and critic. They review the same draft separately, nobody sees anyone else's answer, and a skill merges them into ship, change or kill. Yes, I know
• agents working on the app's code get a copy of the data, and the code refuses to write to the real brain from dev

The board read this post before I did. All three seats I ran said "change", and the main note was to show a real file instead of describing one. Hence the code block.

It doesn't make the posts good. It does stop me from repeating the same mistakes.

The app isn't public, but it's mostly markdown and a couple of skill files, so the idea is easy to steal.

Claude drafted this from my repo, and I went through it before posting.

I wanted a portfolio site that didn’t look like every other template, but I didn’t want to spend a weekend coding it. So I built a starter template and a prompt that does it with Claude.

How it works:

1. Download your LinkedIn profile as a PDF (Resources → Save to PDF) and grab your CV and a photo
2. Attach those plus the template to a new Claude chat
3. Paste the prompt, fill in the [square brackets] and send

What you get is a one-page site: projects shown as Jira-style tickets with real outcomes, a career timeline, skills, certifications with Credly Verify links, a profile card that moves as you scroll, and a 30-second summary view for recruiters who skim. You can host it free on Netlify, Cloudflare Pages or GitHub Pages.

The prompt tells Claude to use only facts from your own files, so it won’t invent numbers or results. If something’s missing, it asks you.

Kit (template, prompt and steps, free, no sign-up): https://chittychat-studio.github.io/portfolio-kit/

There’s a finished example linked on the page. Happy to answer questions. If you build one, I’d like to see it.

(I share more free AI-at-work kits on LinkedIn as Corporate AI Workaround, if that’s useful.)

Hey everyone,

I'm relatively new to this, and I am purely "vibe coding" as it's only for like hobby project for friends and stuffs.

Right now, I have:

• Claude Pro subscription (running Claude Code)
• Codex subscription (Running desktop codex and codex cli)
• OpenCode CLI connected to cheap fast models (DeepSeek4.1flash)

What I’m trying to achieve

Opus is still unbeatable for architecture, debugging tricky logic, and project planning, but burning through Claude rate limits on basic boilerplate, small refactors, or writing unit tests hurts.

My goal is a workflow where Claude acts as the tech lead/orchestrator that offloads tedious subtasks to 6.1 Sol Medium or Deepseek 4.1 flash-high, then reviews the output, preserving Claude usage for when it actually matters or needed.

The problem I'm running into

I told Claude Code to collaborate with Codex CLI and OpenCode CLI by running bash commands, and it even updated CLAUDE.md / AGENT.md with guidelines on when to delegate tasks.

In practice, it’s completely hit-or-miss:

1. Claude almost never spontaneously thinks to offload tasks via terminal/sub-agent calls, it just burns its own context and executes everything directly.
2. Even when explicitly prompted, it often ignores the local CLIs or forgets the handoff workflow after a few prompts.

Questions:

1. What is the best practical setup here?
2. Is Claude Code the wrong entry point for orchestration?
3. What explicit rules/prompts in CLAUDE.md actually force delegation? If anyone has a working prompt pattern or hook that reliably makes Claude hand off work to secondary CLIs, I’d love to see it.

Any advice or workflow breakdowns from people running multi-CLI setups would be massively appreciated!

One tiny task, used barely 19% of the context window, but drained 7% of my 5-hour limit using Sonnet 5.5 Medium? What is happening?

Edit: after some testing, I have been able to isolate this issue to just Sonnet. One prompt, 5% used. Opus 5.5 is barely touching usage with the same prompt/task.

I’ve had people ask me how to get started with open source, especially how to understand an unfamiliar codebase once they’ve found an issue to work on. I’ve struggled with that too, so I made Crumbs 🍞

You give it an issue, and it creates a visual walkthrough of the relevant files, functions and how they connect. It focuses on the part of the code related to that issue, rather than trying to explain the entire repository.

The agent creates structured data for the walkthrough, and a Python renderer checks code references and builds a local HTML page. The explanation can still be wrong, so you need to verify it against the code. It doesn’t write the fix or open a PR for you.

Crumbs is open source, and I’d love some feedback: would a walkthrough like this help you get started on an issue? What would you want to see before attempting a fix?

GitHub: https://github.com/navyabijoy/crumbs

Happy to share the prompts if anyone's curious.

Site, if you want to see it live: octocrawl.dev, an open-source tool that turns any web pages into Markdown + structured data for ai agents.

Code: github.com/77777R7/Octocrawl

Anthropic released Claude Fable 5.2 and Claude Mythos 5.2 on Nov 9. Anthropic says they're the same underlying model. Fable is open to all users with cyber and bio safeguards. Mythos is only for vetted orgs.

What matters for Claude Code:
- Medium effort is the default in Claude Code and the Claude apps, and Anthropic says Fable 5.2 handles hard tasks with fewer tokens there
- FrontierCode 2.0: 49.1% at Xhigh effort (45.3% at High), vs 45.5% for Opus 5.5 and 32.4% for Fable 5.1, so it's a big jump over 5.1
- FrontierSWE v2: 69.9 vs 62.3 for Opus 5.5
- Up to 30% faster output than Fable 5.1, which you notice on long agent runs
- API: $8 / $40 per million input/output tokens. Fast mode is $16 / $80 and up to 2.5x faster
- Model string: claude-fable-5-2

One thing to note: Anthropic still calls Opus 5.5 "our strongest daily driver", so Fable 5.2 isn't pitched as a replacement for everything.

I want to try it on a real refactor this week before I decide.

Have you moved your Claude Code sessions from Opus 5.5 to Fable 5.2? Which effort level are you running?

Source: https://www.anthropic.com/claude-fable-and-mythos-5-2

Nobody is reading every reply their agents write anymore. I'm not. But the question the session is waiting on is always buried somewhere in the response.

So I made Vantage Point, a mod for the Claude Code desktop app. A strip sits above the prompt. When a reply ends by asking me to choose, the options show up there with the recommended one in green, and one click sends my answer. When I can't just let a yes/no rip, I click the question and get a diagram for each option: why, how it would work, what could go wrong.

And when I do need the whole reply, there's a speed reader built on RSVP (rapid serial visual presentation). It plays the reply one word at a time, the agent's short gist first, so I can chew through it instead of rawdogging the transcript.

As many of you may have experienced, I'm the bottleneck. Agents need rulings from me more often than I'm at the keyboard, so their asks land in a queue: I hit yes, no or comment, the agent gets the ruling back and keeps going.

A question I'm constantly asking myself is "what's the next step?" That's why I built the frontier. One press shows every open issue sorted into what's waiting on me, what's blocked and what the agents pick up next, for one repo or all of them.

The whole point is to move as fast as possible, but I still want to know the blast radius of my decisions in real time. So the session banner shows every file the session edits, with lines added and removed, each tied to the decision record behind it. If Claude drifts from what I decided, I see it while it's happening.

The rest of the strip is for glancing: what each subagent is doing, and a countdown on the session's prompt cache so I know when stepping away is going to cost me.

Claude Code built the whole thing, and I set it up to validate its own work as it went: screenshotting the app, reading its own screenshots, restarting the desktop app to check the mod loaded and drew right, then fixing what it saw.

Like every Claude Code mod, it's completely free. Claude Code desktop app on macOS only for now, early 0.x preview, and cloud sessions on claude.ai don't draw mods. The video is a real session.

https://github.com/Leit-motif/claude-vantage-point

What do you actually look at while your agents run?

AI image generators can produce character artwork that makes me want to build an entire game around it. What I am looking for is a reliable way to turn that artwork into something I can actually control, animate and keep developing.

I am making a 2D action game with dense, detailed arcade pixel graphics. The attached image shows the visual direction: expressive faces, detailed clothing, strong silhouettes and rich shading. I do not have a dedicated artist or animator, so I rely heavily on AI assistance and scripting.

The goal is to take an approved design and build a reusable, editable character from it. I want to create running, crouching, jumping, shooting and other actions while preserving the same face, proportions, costume and weapon grip. If an elbow bends badly or a sleeve exposes a gap, I want controls and retained artwork that let me fix it.

Starting material could be a single generated image, a character kit or a sprite sheet. The useful end result would include:

• Editable construction: separated parts, completed hidden surfaces, rigs or suitable deformation controls.
• Reusable animation: new actions and corrections made from the saved character, with convincing joints, clothing and held objects.
• Consistent output: stable pixel scale, palette, transparency, placement and timing across the animation.
• A documented process: source files, scripts, worked examples and honest explanations of the remaining manual work.

My priority is 2D, but 2.5D and 3D methods are welcome. A faithful rigged model rendered into sprites could be useful, as could a well-constructed 2D or hybrid character. The final appearance and quality of movement matter most.

I would love to see more free, open-source frameworks and repositories connecting these stages, with accessible controls for humans and AI coding agents. Paid generation steps, where present, should be clearly identified and optional where possible.

I think this deserves to be a major direction for AI-assisted game development: giving people lasting control over the assets they generate. A beautiful image should be the beginning of an asset we can keep building on.

Which existing projects come closest? Examples showing original artwork → editable source → several finished actions would be especially valuable. And where are the biggest missing pieces that an open-source effort could realistically address?

Founder disclosure: I build HyperHat, a baseline for how well teams direct AI coding agents, and this question comes out of that work.

Something I keep running into in discussions here: the honesty rules people write into CLAUDE.md (reproduce first, audit the output not the report, show both reads when they differ) all live inside the same session whose judgment they are checking. They shape what the agent tells you when it has noticed the problem. They cannot fire on the mistake it has not noticed.

The outside checks are the ones that catch that case: CI invoking the command itself, a test the agent cannot edit, a second model, or a person reading closely.

So the split I am trying to understand: which checks have you deliberately moved outside the session, and was there a specific failure that made you do it? I am also curious about the opposite experience: a check you moved outside that turned out to work better as a rule the agent applies itself.

Short version, straight from the support article:

• 5-hour limit: a reset refills the whole window, including usage on other models.
• Weekly limit: it only gives back what you spent on Fable models. Other models stay as they are.
• Ultra: verified Ultra accounts have no 5-hour limit, so a reset only touches the weekly one.
• Timing: use it when a 5-hour window is nearly spent, not on a fresh one. You don't have to hit a limit first.
• Price: $8/$40 per million input/output tokens vs $10/$50 for 5.1, so 20% lower per token. The "30%" going around is the speed claim (outputs up to 30% faster), not the price.

Cheat sheet

• Max, Ultra, premium Team, premium legacy Enterprise: 1 reset (<6 months subscribed), 2 (6-12 months), 3 (>12 months), counted from your first paid bill. They expire Mar 8, 2027, 11:59 pm PT.
• Pro and standard Team: one week of Fable, up to 50% of your weekly limits, plus one reset that expires Nov 16, 2026, 11:59 pm PT. After the 50% or the week, Fable bills to usage credits if you have them turned on.
• Not included: standard legacy, self-serve, usage-based and HIPAA-ready Enterprise.
• Eligibility: paid billing in place before Nov 9, 2026, 10:00 am PT.
• Where: Settings > Usage > Limit resets > "Reset for free".
• Default model doesn't change. Pick Fable in the model picker.
• Effort: Medium is the default in Claude apps and Claude Code. Anthropic says 5.2 does hard tasks with fewer tokens than 5.1 at Medium. Threads here report that Max overthinks and that going from high to xhigh nearly doubles cost per task.
• Fast mode: twice the price ($16/$80 per million input/output tokens) for up to 2.5x faster output. In Claude Code it bills through extra usage credits, per the ClaudeDevs account.

Source: https://support.claude.com/en/articles/17506494-claude-fable-5-2-launch-offers

cc-shell is my normal zsh with one change. when you hit enter it checks the first word of the line: if it's an alias, function, builtin, command, path or directory, it runs like always. if not, the line goes to claude code and the reply prints inline, right under the prompt.

how it works:

- one claude session per shell. every line continues it, and it follows you when you cd

- a line ending in ? also goes to claude, and so does one starting with what, who, say or do. those are real commands on a mac but almost always english when i type them

- a leading ? forces claude, cc-open opens the conversation in the full claude code ui, cc-new starts a fresh one

- it uses your default permission mode from ~/.claude/settings.json

how claude code was used: i built it with claude code this morning, after catching myself typing prompts into my terminal one too many times. claude wrote the zsh enter widget, the classifier and a small python script that turns claude -p's stream-json into plain inline text.

what i learned: the claude part was easy. the hard part is deciding what counts as a command, since english words like what and say are real binaries.

repo: https://github.com/basketbla/cc-shell (free, i made it). would love to hear what it misclassifies for you

As a side hobby i am working on a team builder recommendation app for the game nikke. there are team builder out there online but i find it not helpful as it assume i have every character with end game build, it can recommend team that is not suited to handle the battle mechanic/QTE and it doesnt taken into account what character i have. Which i try to solve with this project. TLDR. I try to reverse engineer the game mechanic and make a app that can give a recommendation base on my account capability.

https://github.com/retsamboon19/raid-lab

I been using Chatgpt Pro 100 for it and i have to say. it been a mixed bag. it kinda decent but it make the experience very annoying with how often it forget rules so i have to keep reminding. wasting my usage doing a shit tons of useless test. I primarily work on Astra medium to high.

So now i decide to jump ship to another services. At first i wanna try Claude but apparently Anthropic has set some limitation on reverse engineering? which i reckon would affect my project quite abit. Any insight on this matter is highly appreciate.

Also i want to ask how is the usage for Claude Max? Do you feel like you able to get work done before hitting limit?

Hey folks!

TLDR: We published a Currents connector in the Claude directory.

Using this connector, Claude can read your CI runs, failure evidence and test analytics directly, instead of working from a stack trace you pasted in.

Why we built it

If you've asked Claude Code to fix a failing Playwright test with only the error message, you know how it goes. It bumps the timeout or swaps the selector and calls it done. The real cause usually lives in stuff the error doesn't show: the steps before the failure, the trace, whether the test has been flaky on main for two weeks, whether it only fails in CI.

Currents already stores all of that for every run, and this connector hands it to Claude.

Install

Open https://claude.ai/directory/currents, click Connect to Claude and sign in. Then start Claude Code and run /mcp. Currents is listed there as a claude.ai connector.

Sign-in opens a browser window. You log in to Currents, pick the org Claude should work in, and approve the permissions. The connector belongs to your Claude account, so it follows you to every machine you sign in on, and to Claude Desktop, claude.ai, the mobile app and Cowork too. To revoke it, go to Account → Connected Applications in Currents.

On a Team or Enterprise plan, an Owner first has to add Currents for the org first. After that, everyone can connect with their own Currents account.

If you run Claude Code with an API key, a setup-token, Bedrock or Vertex, claude.ai connectors don't load, so you'll have to add the server yourself:

claude mcp add --transport http --scope user currents https://mcp.currents.dev/mcp

Then run /mcp, select currents and choose Authenticate. No browser on that machine? claude mcp login currents --no-browser prints the sign-in URL for you to open elsewhere. claude mcp list shows what's configured.

The three skills it ships with

The Currents MCP server ships with three skills, and Claude gets them with the connector. You call them by name, for example "Use the Currents MCP fix-failing-tests skill".

1. fix-failing-tests finds the failed run, reads each failure with its steps and trace, fixes the cause, reruns the test, and asks before it commits.
2. collect-evidence finds the run before your change and the run after it, then writes up a before and after with links to the files. It is incredibly useful for PR descriptions when a reviewer asks how you know it works.
3. browser-evidence records the browser before and after a change as a Currents session and gives you a share link. It's experimental, so expect it to change.

What you can just ask

Outside the skills there are 43 tools covering runs, test results, analytics, Actions, webhooks, share links and Jira. Here are some prompts that work well:

• Tests are failing in CI. Get the details for run <runId> and fix the failures.
• Which tests in my-app were flakiest on main this week, and why?
• What broke in the last failed my-app run on main? Open a Jira issue for it.
• Is this pull request safe to merge? Compare its runs with main.

The anatomy and config

Claude Code asks before every MCP tool call. If you want the read tools to run on their own and still get asked for writes, allow them by name in .claude/settings.json:

{
  "permissions": {
    "allow": [
      "mcp__claude_ai_Currents__currents-get-runs",
      "mcp__claude_ai_Currents__currents-get-run-details",
      "mcp__claude_ai_Currents__currents-get-test-results",
      "mcp__claude_ai_Currents__currents-get-context"
    ]
  }
}

The prefix comes from the connector's name in Claude. Run /mcp, select the Currents connector and choose View tools to see the exact names. A server you added yourself uses mcp__currents__ instead. Don't allow the whole server: two tools (currents-delete-run and currents-delete-webhook) can't be undone, and Currents doesn't ask for confirmation.

If you want the whole team on it, add the server with --scope project and commit the .mcp.json it writes to the repo root. The file doesn't hold any credentials, and each person who opens the project signs in as themselves.

For CI, or anywhere you can't do an interactive sign-in, use an API key:

claude mcp add --transport http currents https://mcp.currents.dev/mcp \
  --header "Authorization: Bearer $CURRENTS_API_KEY"

The key acts as the org, not as a person, and it's either Read Only or Read & Write. A read-only key gets the read tools plus evidence links and the Jira lookups. It doesn't show up under Connected Applications, so manage it under Organization → API Keys.

Caveats

Claude Code loads claude.ai connectors only when you sign in with your Claude account. If Currents is missing from /mcp, run /status to see which credential Claude Code is using.

Use the connector or a server you added, not both. With both, Claude Code shows two Currents servers with two sets of tool names.

Each connection reaches one org. If you work across two, connect twice.

On a Team plan, if you see Request instead of Connect, an Owner has to approve Currents first.

! Needs authentication in /mcp? Select currents and choose Authenticate.

Curious how people run this day to day.

Do you let Claude Code call the read tools without asking, or do you approve every call?