AffableSpatula

5 ms·

1.
by AffableSpatula 3mo ago
Sync your Claude Design projects into your repos (list/pull/push) straight over the API; perfect for scripts and there's a skill for agents too. `npx claude-design` `npx skills add mikekelly/claude-design`
2.
Gap: Give AI agents secure access to your accounts – without sharing credentials(github.com)
1 points by AffableSpatula 8mo ago|0 comments
3.
by AffableSpatula 8mo ago
You're absolutely right! I apologise — hopefully you can forgive me.
4.
by AffableSpatula 8mo ago
yep this is exactly how I use the main agent too, I explicitly instruct to only ever use background async subagents. Not enough people understand that the claude code harness is event driven now and will wake up whenever these subagent comp
5.
by AffableSpatula 8mo ago
Claude already had subagents. This is a new mode for the main agent to be in (bespoke context oriented to delegation), combined with a team-oriented task system and a mailbox system for subagents to communicate with each other. All integrat
6.
by AffableSpatula 8mo ago
I don't know what you're referring to but I can say with confidence that I see more efficient token usage from a delegated approach, for the reasons I stated, provided that the tasks are correctly sized. ymmv of course :)
7.
by AffableSpatula 8mo ago
I think you've misunderstood what this is.
8.
by AffableSpatula 8mo ago
Task sizing is important. You can address this by including guidance in the CLAUDE.md around that ie. give it heuristics to use to figure out how to size tasks. Mine includes some heuristics and T shirt sizing methodology. Works great!
9.
by AffableSpatula 8mo ago
a similar question was asked elsewhere in the thread; the difference is that this is tightly integrated into the harness
10.
by AffableSpatula 8mo ago
I've seen more efficient use of tokens by using delegation. Unless you continually compact or summarise and clear a single main agent - you end up doing work on top of a large context; burning tokens. If the work is delegated to subage
11.
by AffableSpatula 8mo ago
it's my repo - it's a fork of cc-mirror which is an established project for parallel claude installs. I wanted to take the least disruptive approach for the sake of using working code and not spelunking through bugs. Having said t
12.
by AffableSpatula 8mo ago
yeah I tend to agree. They're must be reaching the point where they can automate the analysis of claude code prompts to extract techniques and build them directly into the harness. Going up against that is brave!
13.
by AffableSpatula 8mo ago
Delegation patterns like swarm lead to less token usage because: 1. Subagents doing work have a fresh context (ie. focused and not working on the top of a larger monolithic context) 2. Subagents enjoying a more compact context leads to bett
14.
by AffableSpatula 8mo ago
The feature is shipped in the latest builds of claude code, but it's turned off by a feature flag check that phones home to the backend to see if the user's account is meant to have it on. You can just patch out the function in th
15.
by AffableSpatula 8mo ago
ha! The default system prompt appears to give the main agent appropriate guidance about only using swarm mode when appropriate (same as entering itself into plan mode). You can further prompt it in your own CLAUDE.md to be even more resista
16.
by AffableSpatula 8mo ago
The difference is that this is tightly integrated into the harness. There's a "delegation mode" (akin to plan mode) that appears to clear out the context for the team lead. The harness appears to be adding system-reminder bre
17.
Claude Code's new hidden feature: Swarms(twitter.com)
521 points by AffableSpatula 8mo ago|335 comments
18.
Beyond Ralph – Experiments in Claude Code Context Wrangling(twitter.com)
1 points by AffableSpatula 8mo ago|0 comments
19.
Show HN: Overwatch.nvim – Neovim plugin for collaborating with AI coding agents(github.com)
2 points by AffableSpatula 8mo ago|0 comments
20.
Show HN: Promode – Claude Code meta for its hidden "Team Mode"(github.com)
2 points by AffableSpatula 8mo ago|0 comments
21.
Show HN: Promode for Claude Code(github.com)
1 points by AffableSpatula 9mo ago|0 comments
22.
by AffableSpatula 2y ago
"You can build your own thing using card emulation via apps, but you will take all the risks." right! This is exactly what I've developed. I've built a new NFC application, with its own PKI infrastructure, that's de
23.
by AffableSpatula 2y ago
Hi there, author here! I think you've highlighted a couple of things worth clarifying in the doc: 1. Apple having just announced it is opening up NFC to developers means that both major mobile platforms can now act as responding device
24.
Show HN: A1 – Faster, Dynamic, More Reliable NFC Transactions(github.com)
29 points by AffableSpatula 2y ago|4 comments
25.
Agent K – An autoagentic AGI that is self-evolving and modular(github.com)
5 points by AffableSpatula 2y ago|0 comments
26.
Overlay: Supercharging Tap to Pay(newpayments.substack.com)
2 points by AffableSpatula 2y ago|0 comments
27.
The card payments you use every day are stunting economic growth(newpayments.substack.com)
1 points by AffableSpatula 2y ago|0 comments
28.
by AffableSpatula 5y ago
The database is postgres under the hood which provides atomicity. We verify the signature of signed pieces (and signed deeds) and then commit the transaction to postgres with a digest of the content (which has a unique constraint on it) - t
29.
by AffableSpatula 5y ago
Great question! :) Right now the UI for creating deeds is from author to owner. We will add the interface for owners to sign on ownership with further deeds in the future. This felt like a feature to leave out for early launch.
30.
by AffableSpatula 5y ago
The application code that runs this isn't open source at the moment but there's no reason it couldn't be packaged up. Either way, the intention is to expose this as an API so that people can write their own open source client

More ›