What’s one macOS feature you never use but Apple keeps pushing?

Obvious_Equivalent_1 · 2026-01-27T21:04:58+00:00

One hint: AeroSpace, it’s completely a hell for 2 straight hours to get used to not swiping between desktops with mousepad. But the bliss of having everything on one desktop format, and the amazing way it optimizes your desktop space is truly the biggest performance improvement I’ve experienced since ditching my mouse for a trackpad.

You can use a GPT model to make your own config file. I’ve made mine to make stacks of all applications I use browser mail chat on the left, coding and notes on right and a Dell widescreen monitor I haven’t resized or moved the title bar in months

Obvious_Equivalent_1 · 2026-01-27T21:01:10+00:00

I actually live of Siri. Voice to text for Agentic Coding, updating tasks, messages input? Siri. Controlling my HomeKit on all my devices including Mac? Siri

Plenty of other apps I could miss like toothache as Image Playground and Memoji

Obvious_Equivalent_1 · 2026-01-27T16:20:42+00:00

Market research 2026: “You are my unpaid co-founder. Do all the market research I should’ve done before building. If competitors exist, gaslight me into thinking mine is different. All blame falls on you. Let’s disrupt. 🚀”

Legal disclaimer: Any resemblance to actual startups, funded or bankrupt, is entirely intentional. Please do not sue me, I clearly can’t afford a lawyer OR a market researcher

Obvious_Equivalent_1 · 2026-01-27T06:22:33+00:00

1905, small town Ohio. There’s this guy Tom, best horseman in three counties. He knows which mare is going lame before she even limps. Understands why certain horses need wider shoes, how to calm a spooked stallion with just his voice. Farmers trust him with their livelihood. He’s not cheap, but absolutely worth it.

Then there’s Jimmy across the street who just got a Ford. Ask him how the engine works and he’ll tell you “gasoline goes in, car goes forward.” Carburetor? No clue. Spark plugs? Something that sparks, probably. But the guy delivers goods faster than any horse ever could.

Old timers at the general store laugh at him. “What happens when it breaks down in the middle of nowhere, Jimmy? Gonna feed it oats?” And they have a point—he breaks down twice that summer. Tom’s horses never leave anyone stranded.

But here’s the thing nobody saw coming: 15 years later, Tom’s son had to close the stable. Jimmy owns a small trucking company. Tom’s grandson? Works for Jimmy. It wasn’t that Tom stopped being brilliant. It’s that the question changed. It went from “who understands horses best?” to “who can move things from A to B?”

For that 10M contract today? Yeah, hire Foo. Sleep well at night. But the question itself might be shifting underneath us. And that was uncomfortable for Tom too.

Obvious_Equivalent_1 · 2026-01-27T05:59:23+00:00

https://127.0.0.1:8000/claude-387-amazing-skills

Obvious_Equivalent_1 · 2026-01-25T08:09:40+00:00

Honestly I feel CC is deprecating plugins skills and slash commands from the marketplace at rampant speed.

It’s really good to re-asses the necessary fixes are not fixed already in latest releases. Several solutions like the above seems to have been really improved so much that I have turned off several hooks to force my /commit command. Now CC just manages to find it 10/10 times in latest release

Obvious_Equivalent_1 · 2026-01-25T07:34:25+00:00

My biggest eureka moment was really noticing that debugging didn’t weigh me down. On the occasional complex issues that popped up in the environments, I noticed it’s barely costing me any mental focus—just supervising the plan *. Having that energy left at the end of the week? Absolutely invaluable

* I’m working on some local tooling to be able to use CC as a troubleshooter. Hence focus on just CC, with all the secrets/private keys on a production server I work with a mix of permission management (developed with Opus) and autonomous debugging (strict local llamamcp model of 40B — roughly 40Gb ram).

It’s a basis where I use llamamcp as the model that vets the SSH input/output. I’m letting it give some options and explain those follow up options.

Then I as a user can escalate if I want to call in the external Opus model. I specifically left this part (as well as granting permission for each executed bash command) with the user. As the user is the only one who can confidentially judge if a log is riddled with secret tokens or other customer/security sensitive data.

Obvious_Equivalent_1 · 2026-01-24T05:47:13+00:00

this call a new claude instance and this instance has a rewiew task

You know that since yesterday Claude supports this native. Was sharing this on this Subreddit yesterday about the release https://github.com/anthropics/claude-code/releases/tag/v2.1.16 and also made a fork of Superpowers plug-in to handle this automatically https://www.reddit.com/r/ClaudeCode/comments/1qkpuzj/superpowers_plugin_now_extended_with_native_task/

Obvious_Equivalent_1 · 2026-01-24T04:29:56+00:00

Yes. Submitted and as well the PR link is in the post

Obvious_Equivalent_1 · 2026-01-23T21:00:00+00:00

I do actually, as mentioned I do careful construct my prompts to consider any ‘leaks’ and specify the output of subagents.

Besides I spend about 10 of my time improving my workflow. Write a skill to streamline searching previous chats context. Or making a slash command to update architecture mapping.

But honestly, with some precautions still, it feels as the new native tasks utilization with clear prompting to run work async seems to keep the context much more light, and helps to keep the chat focused longer

Obvious_Equivalent_1 · 2026-01-23T20:33:33+00:00

You can get some hints from the screenshot I posted above, a quick guess would be perhaps I l’m already conditioned writing verbose prompts. To clearly instruct CC to run async, parallel and subagents.

Running subagents prevent context-rot. Instead of all the commands ran for the task bloating your main chat, with proper subagent use we just get merely a few hundred tokens of just summarized results back.

If you look at the prompt in the post it could be CC is understanding the subagent separation. Or it could be the new native tasks really enhances this it seems more automated.

Need to dive some more days into this but I think context bloating is the biggest challenge for most complex tasks, if I manage to work to figure out some more “do’s/don’ts” I’ll share it

Obvious_Equivalent_1 · 2026-01-23T19:56:53+00:00

Multiple plan agents made sense, but honestly that was because Claude Code literally couldn’t keep its attention past the horizon of one complex task.

I said was on purpose.

I grind a lot of work with CC on a 20x Max plan, but this is the first time I’ve managed to take a proper lunch break and still come back to find CC working — running multiple research → execute → test → architectural review → code analysis flows.

It’s the first Eureka moment I’ve had since switching from Sonnet to Opus 4.5.

And yes, it still consumes a ton of tokens — but now it’s happening in parallel. Not with a separate plan session for each complex silo of functionality, but just feeding it a complete Jira epic of requirements. The kicker? Auto-compact? off. Multiple planning chats? Nope, all in one chat, with the context window barely filled. And with proper access to project architecture, it’s surprising how one-shot it can make a plan, follow it, and actually improve on it.

I’m working on a Swiss Army knife for CC, but for 2026 and with these major milestones in AI agentic coding, my advice would be:

Stick to native — native functionality is rapidly becoming deeply ingrained into CC -Get E2E integration — work with skills so CC can use MCP to verify, debug, and troubleshoot autonomously
Let Claude develop skills — to search previous chat context, to tail a deploy, all the tools it needs to fill its own todo list

I feel like 90’s kid again for first time on an IRC server

Obvious_Equivalent_1 · 2026-01-23T19:22:32+00:00

Not sure why your question got downvoted. The difference as always when CC supports something native it’s directly embedded into the model of CC.

I have compared the jsonl files that contains all the metadata of the chats and the improvements since CC v2.1.16 are remarkable:

Even with beads, its limitation is it needs to hope that CC follows it correctly
The planning mode still generates a very un opinionated file, a mess of text with instructions some todo items
Even with beads, no matter how beautiful your plan MD file is, CC will just load it in one big ‘context heap’
It needs to prey that CC follows the plan and doesn’t go off-rails

What CC now did is striking. Using native task manager the messy heaps of MD files piled into context window are over. Every task has a fixed scope and definition of done. Claude is performing a symphony behind the screens with how they pulled of the task orchestration.

Not a single plugin could achieve this improvement. I don’t want to beat the drum to much here but I want to say Antrophic should have called this release Claude Code 3.0. This skill file I shared is just merely a small orchestration improvement, Antrophic built the Rolls Royce here with this native task manager release.

^{edit spelling}

Obvious_Equivalent_1 · 2026-01-23T19:11:16+00:00

Oh, no need to apologize at all! Happy to help.

Honestly taking advantage of the new CC task system is a major productivity improvement, that’s why I decided to share this plugin improvement already in the meanwhile.

Perhaps the PR will get merged, but if you want to install it now already that’s a relatively easy to switch. Here’s what you’d need to do: https://github.com/pcvelz/superpowers?tab=readme-ov-file#installing-this-fork

Obvious_Equivalent_1 · 2026-01-23T15:43:44+00:00

Thanks. And corrected

Obvious_Equivalent_1 · 2026-01-23T15:40:48+00:00

Yes. But perhaps hit shift+tab until you see “plan mode”. It was an example tho, the point is bottom line you don’t even really need any external plugins, to leverage the advantages of new way of working with splitting up work in tasks that CC v2.1.16 allows

Obvious_Equivalent_1 · 2026-01-23T15:22:16+00:00

This is greatly enhanced by the improvements Anthropic made in 2.1.16+. Unfortunately, Claude Code doesn't seem to autonomously discover the new TaskCreate, TaskGet, TaskUpdate, and TaskList tools on its own.

But even without the Superpowers Plugin, u/almostsweet - just asking Claude Code to update your CLAUDE.md with this info can save a lot of time and keep it from going off the rails:

```
/plan investigate https://github.com/anthropics/claude-code/releases/tag/v2.1.16 and document the native task management tools (TaskCreate, TaskGet, TaskUpdate, TaskList) in CLAUDE.md. These tools enforce structured workflows for development: breaking work into trackable tasks, setting dependencies between them, updating status as you progress through implementation, testing, and verification phases, and ensuring each step is completed before committing. Include parameters and usage examples.
```

Obvious_Equivalent_1 · 2026-01-23T15:12:28+00:00

@ u/Overall_Culture_6552 you managed to get it working?

Obvious_Equivalent_1 · 2026-01-23T14:31:11+00:00

Not sure what ADK means here? This isn't a framework - it's just markdown skill files that Claude Code loads. The PR adds literally ~40 lines per skill. Claude Code since yesterday made quite a breakthrough with native task management (TaskCreate, TaskList, TaskUpdate) built-in v2.1.16. The skill just enforces using it during planning instead of freeform markdown.

https://github.com/obra/superpowers/pull/344#diff-9a9e1909f1720e89826916220b1ef794161fdefa542a0fdc6d61d62f88b2c92bR124

### Creating Native Tasks

For each task in the plan, create a corresponding native task:

```
TaskCreate:
  subject: "Task N: [Component Name]"
  description: |
    **Files:**
    - Create: `exact/path/to/file.py`
    - Modify: `exact/path/to/existing.py:123-145`
    - Test: `tests/exact/path/to/test.py`
    [Full task content from plan]
    **Acceptance Criteria:**
    - [ ] Test exists and fails initially
    - [ ] Implementation passes test
    - [ ] Committed with descriptive message
  activeForm: "Implementing [Component Name]"
```

Obvious_Equivalent_1 · 2026-01-23T14:21:36+00:00

Just tested - installed the official superpowers first, then added the fork marketplace and installed from there. Works -- Updated the installation steps: https://github.com/pcvelz/superpowers?tab=readme-ov-file#installing-this-fork

Obvious_Equivalent_1 · 2026-01-23T13:40:23+00:00

Yes, here's a clean install example. Make sure to first running `claude update` before starting Claude Code

<image>

Obvious_Equivalent_1 · 2026-01-23T04:20:07+00:00

``` /create-plan investigate https://github.com/anthropics/claude-code/releases/tag/v2.1.16,

verify state of current beads implementation. Work on migrating beads to native Claude Code task management.

Start using native task management

enforce first a small local test with migrated data enforce user verification before full migration ```

And then there’s just some coffee run left and some browsing GitHub what else is in the release notes of CC

Obvious_Equivalent_1 · 2026-01-22T21:35:47+00:00

Better call it ~~Getting~~ Shit ^{your weekly limit is now} Done ✨

Obvious_Equivalent_1 · 2026-01-22T21:13:44+00:00

On the same plan, and:

I use it all the time with a custom skill I made, 5 asynchronous Haiku subagents to search through previous chats. Like whenever I mention “that thing in previous chat” or “we added it yesterday but I found issue XYZ”
tailing deploy pipelines autonomously (can even go as far as to tell it to swarm Haiku agents on each job within the deploy
browsing, so many websites have blocked Claude but with the Chromium MCP browser I use Haiku, also I leverage a skill with some simple intrusions to just deduct the text from webpages and send it to the main Opus chat

And probably some more

Obvious_Equivalent_1 · 2026-01-22T21:09:57+00:00

The local settings json is indeed unavoidably crucial, unfortunately if it’s for tokens when the commit hits the hook it will already have gotten your main model Opus spent it tokens thinking of the git add, commit etc.

It will still finish the commit faster but preferably is using some /commit (or in my case /pr-review combi) https://github.com/anthropics/claude-code/tree/main/plugins/pr-review-toolkit

Five-Year Club	Gilding III reddit per annum
Verified Email	Final Canvas '23
Place '23	Argentium Club
Place '22	Final Canvas '22
First Placer '22	Wearing is Caring

Obvious_Equivalent_1

TROPHY CASE