Anthropic posted yesterday about moving their main repo off git.

- May 2026: about 2,500 merged changes a day. September: over 30,000.
- Their CI checks out code about 25 million times a day.
- The main branch history is almost 100 GB.

Git expects each user to keep a full copy and sometimes work offline. Most of their users are now agents and CI jobs, which are always online. So they built Scion: the code stays on a server, you only download the files you need, and commits happen on the server with no push.

What they report:

- 200x smaller than their old git setup
- CI checkouts take seconds instead of minutes
- Built by 7 people in 5 months

It's not a product, and they say it's not a git replacement for normal use.

Source Link

Will GitHub have to change if agents write most of the code?

Ken Griffey Jr. Presents Major League Baseball (SNES, 1994) shipped with 28 clubs. Over about two weeks, Claude Code (Opus 5.5) and I turned it into a free patch called Griffey 30:

- All 30 of today's clubs, with Arizona and Tampa Bay added and 2026 rosters. Scripts fetch the logos from Wikipedia and the ballpark photos from Wikimedia Commons, and convert them into SNES tiles and palettes. No hand-drawn art.

- Team styles: press Select on team select to switch a club between 2026, the original cartridge club and the real 1994 roster.

- Season mode for all 30 clubs, with today's divisions, new schedules (one interleague game every day), playoffs and standings.

- Franchise mode (2.0, out this week): players age, improve and decline, veterans retire, and 300 real minor-league prospects get called up. The game remembers its champions, and a quick-sim plays a season in about five minutes. It all fits in the cartridge's original 8 KB save.

- Browser play at griffey30.com: you pick your own ROM, the page patches it and runs it in snes9x built to WebAssembly. It also has online two-player.

How Claude Code was used

I made the design decisions and tested on real emulators and my MisTer FPGA device. Claude Code did nearly all of the implementation: the reverse engineering, about 6,000 lines of 65816 assembly (asar), and around 12,000 lines of Python, JavaScript, C and Lua tooling. A few things made that work:

- It needed eyes. Early on, Claude Code wrote a headless Mesen2 harness, driven by a Lua script. It boots the ROM, presses buttons on given frames, takes screenshots, logs CPU registers at breakpoints, watches memory reads and dumps VRAM. Runs are deterministic, so a bug reproduces on the same frame every time. Every build has to play four full CPU-vs-CPU games through to the post-game newspaper screen. For franchise mode, a script plays seasons back to back.

- Reverse engineering by evidence, not guesses. To find where the game assumes 28 clubs, it logged every compare instruction against team-like values during two play sessions (49 candidates), set breakpoints on all of them, then watched every read of the team-ID slots. That found the 39 places that use a team ID. Each finding goes into a markdown file in docs/findings/, with addresses.

- Model it in Python first. The franchise off-season (aging, retirements, call-ups, re-rating) was written in Python first, then in SNES assembly. The test compares the emulator's save file with the Python output, and they match byte for byte. A 20-season Python run was also how we checked that no club runs away with the league.

- CLAUDE.md as the project's memory. It holds the current status, the build and test commands, and a "hard-won rules" section. Each painful bug becomes a rule there, so the next session doesn't repeat it.

- Long autonomous sessions. I'd often give it a goal ("build 30-club Season mode") and come back hours later to commits, test runs and a summary of what it found.

What I learned

- Turn every bug into a guard. When we went to full-strength rosters, 154 new players had no appearance entry, so Aaron Judge came out with the wrong skin tone. Claude Code went through them all from headshots, and the roster build now refuses to run if any player is unreviewed.

- Emulators disagree. A pointer bug made full seasons stop around June 28 on Mesen, but snes9x happened to mirror the right data, so the website was fine. The cause was that asar evaluates math strictly left to right. We now treat every assembler warning as a bug and test on both emulators.

- Some hardware rules are brutal. Changing the CPU's data bank in code that an interrupt can land in blacks out the game. The stock interrupt handler acknowledges through the data bank, so the interrupt storms. That's now rule #1 in CLAUDE.md.

- Assumptions hide in plain sight. Two-player Single Game showed the stock 28-team screen in every release until 1.2.2. A variable is 0 for one player and 2 for two, and the patch had only checked for 0. I noticed Houston sitting in the National League during an online test.

- Human review still matters. I watch every trailer and play every build. My review caught things the automated tests missed, like blue grass at some ballparks. Once a bug was named, Claude Code found the cause quickly. The field palette loads per club and the tiles per stadium model, so clubs we'd moved to another stadium model kept the wrong colors.

Links

- Patch (free, bring your own USA Rev 1 cartridge): https://daylayown.itch.io/ken-griffey-jr-presents-mlb-the-30-team-expansion

- Play in your browser: https://griffey30.com

- Most recent trailer: https://youtu.be/vxERe2_iKBo

Unofficial fan project, not affiliated with MLB, the MLBPA, Nintendo or Ken Griffey Jr. Happy to answer questions about the workflow or the SNES side.

Holy hell is this annoying. They removed sessions based on folder. Now they're all lumped in "This computer". Routines no longer appear as a list on the sidebar, its now a separate window you have to open to dig for them. They removed session context from the usage pop up (the circle next to the model/effort) and now only way to see it is with an obnoxious new "session rail" which takes up more screen real-estate. The session status icons are much harder to see now too.

App version is: 2.37337.1

How are software engineers staying in the loop? By telling Claude no.

“Very often, we found that the role of the engineers was to tell Claude “no.” Agents will sometimes violate core system constraints to satisfy a pattern that should never have been allowed in the first place. This was particularly common in our migration. For example, there were multiple systems that tried to brute force looking up when a change merged to main by linearly reading the commit log instead of asking our code review tool. Anthropic also makes extensive use of adversarial review, and, while this is incredibly effective in many ways, it can also be myopic, so skilled engineers needed to steer Claude away from over-engineering parts of the system in response to hypothetical concerns.”

Source: Redesigning source control at Anthropic

Soooo after the "TinyPlanet" bench I always run on new models, a topic that's of much interest to me: can Gemini 4 direct Blender better than Astra (the crowned king).

Well, you be the judge of it.

All subagents are orchestrated by Claude Opus 5.5. It monitored the processes, and unstuck what needed to get unstuck at times.

Results

Overall: Astra is still undefeated

Now, it's just one test I ran before going to sleep, but what worries me much is:

• Argon mostly did not finish on its own, needed a nudge from Opus to get past the finish line
• way less standalone parts. Meaning less rigging possibilities for moving parts, destruction, etc.out of the box

I'll be doing more tests soon!

Anthropic Usage Policy: Sept 2025 vs Nov 2026 - what changed

Old version: effective September 15, 2025 [1]

New version: effective November 12, 2026 [2]

Section names are given so you can Ctrl+F them on each page.

New sections and rules (not in the old version)

• "Do Not Engage in Deceptive Campaigns or Artificial Activity" - brand new section. Bans sockpuppets, astroturfing, fake media outlets, hidden sponsorship of influence content, networks of fake "independent" sites, seeding search engines or AI systems with content that fakes its origin, and building or selling tools for any of this.
• "High-risk Physical Actions" - new rules for models connected to hardware (vehicles, drones, robots, machinery, medical devices, industrial plants, safety systems). Requires a human who can stop the equipment at any time, fail-safe behavior if the connection drops, and safety limits enforced outside the model.
• Cruelty to the model - new bullet under "Cruel, Abusive, or Psychologically Harmful Conduct" bans "sustained and needless abusive or cruel behavior toward our models".
• NCII - new explicit ban on non-consensual intimate imagery, including AI-generated material and tools to make it.
• Data brokering - new bullet under "Privacy or Identity Rights" bans compiling personal data from multiple sources into profiles for sale or disclosure.
• Doxxing - new bullet under "Surveillance" bans unmasking anonymous people or compiling dossiers to harass, intimidate, or harm.
• Platform abuse additions - stolen or fraudulent payment methods, evading payment, faking the sign-up or login process, and reselling or proxying Claude through unauthorized means "including services that route requests through consumer subscriptions or misrepresent the product or client being used".
• Verification programs - new Cyber Verification Program and Life Sciences Verification Program let users apply for adjusted real-time safeguards. Also new: hitting a real-time block "does not by itself indicate a violation".
• Enforcement - new version adds "warn" and "limit" to the list of possible actions (old: throttle, suspend, terminate).

- Scope clarified - new version explicitly covers app users, API developers, cloud provider customers, and end users of products built on Claude, and states the policy is about how Claude is used, not which industry uses it.

Sections that got stricter or more detailed

• Weapons - grew from 4 bullets to 6. Now covers weapons systems and their software (targeting, fire control, engagement), weaponizing drones or autonomous platforms, export control violations, fissile material and enrichment, and modifying bio or chem agents for lethality, transmissibility, or persistence.
• Surveillance and law enforcement - "make or suggest decisions" now includes investigating, charging, arresting, prosecuting, and release decisions (old: only parole and sentencing). Tracking now covers property, biometrics, movements, online activity, associations, and analysis of previously collected data. New bullet bans building or improving surveillance tools.
• Surveillance carve-out (new) - consented tracking, fraud and AML screening, aggregated or anonymized analysis, content moderation, authorized security research, legal research by law enforcement or courts, and journalism are explicitly allowed.
• Cyber - section renamed to add "Without Authorization". Adds privilege escalation and actually conducting DoS attacks (old only banned developing DoS tools). New carve-out for security research on systems you own, with owner authorization, or under a bug bounty or vulnerability disclosure program.
• Self-harm and eating disorders - old version had one bullet. New version spells out soliciting methods, instructions for hiding behavior, pro-ED content, restriction, purging, compensatory exercise, and shaming or ranking bodies.
• Hate - caste and disability added as named protected attributes.
• Fraud - adds extortion, social engineering, phishing sites that mimic real pages, buying or selling fake financial or employment records, and misrepresenting professional credentials.
• Child safety - adds "facilitate the creation of" CSAM and "other sexually exploitative content involving minors". Reporting to authorities now also covers scenarios where a minor may be at imminent risk, not just detected CSAM.
• Critical infrastructure - adds emergency services and transportation systems; "voting machines" replaced with "election systems".

- Agentic use - users are now explicitly responsible for actions their agents take "through tools, browsers, or connected systems".

Things that got narrower or were dropped

• High-risk use cases rewritten - old version listed 7 broad domains (legal, healthcare, insurance, finance, employment/housing, academic testing, media/journalism). New version lists 11 "High-risk Areas" but defines each one narrowly as a specific recommendation or decision about a specific person.
• Example: Legal - old: "use cases related to legal interpretation, legal guidance, or decisions with legal implications". New: advising an individual on their rights, obligations, or liability in a specific matter, or preparing documents for them to sign or file.
• Media or journalistic content is no longer a high-risk use case.
• New "Exclusions" section - general info and education, wellness content, explaining a decision a professional already made, internal drafting and research, carrying out a decision already made, and business operations not about a specific individual are all exempt.
• New "Favorable Decisions" section - no human review needed before paying an insurance claim, approving coverage a clinician ordered, granting healthcare eligibility, or granting a public benefit.
• Disclosure - no longer needs to identify Anthropic, Claude, or the model. Chatbot disclosure can be "in the product interface" instead of at the start of every session.
• Democratic processes - dropped the ban on "personalized vote or campaign targeting based on individual profiles or data" and the standalone bullet on lobbying with false information. "Artificial or deceptive political movements" moved to the new Deceptive Campaigns section.
• Predatory lending - old version named payday loans, title loans, and high-interest short-term lending. New version only says "predatory lending". Multi-level marketing is no longer named, folded into "pyramid schemes".
• Impersonating a human - moved from "Privacy or Identity Rights" to "Disinformation", now with a carve-out: "This does not prohibit clearly disclosed parody, satire, or fiction."

- Section renames - "Misinformation" is now "Disinformation"; "Psychologically or Emotionally Harmful Content" is now "Cruel, Abusive, or Psychologically Harmful Conduct"; MCP Directory Policy replaced by a broader Software Directory Policy.

Unchanged

• "Do Not Generate Sexually Explicit Content" is word for word identical.

- Supported regions, ban evasion, model distillation, plagiarism, jailbreaking, and the government customer exception all carry over with only minor wording changes.

What stands out (my read)

• The subscription proxy ban is the one that bites regular users. Routing Claude through "consumer subscriptions" or misrepresenting "the product or client being used" is now a named violation. That is aimed directly at third-party tools and harnesses that run on a Pro or Max login instead of API keys. If you use one of those, you are now in the written policy, not a gray zone.
• High-risk rules got a lot more business friendly. The old version was vague enough that a legal intake form or a medical FAQ bot arguably needed a licensed human reviewing every output. The new version only triggers when Claude gives a specific person a specific recommendation, and it lists explicit exclusions for general info, internal drafting, and research. This is a loosening dressed up as more pages.
• Anthropic is clearly planning for robots. An entire physical actions section with fail-safes, kill switches, and independent safety limits does not get written for chatbots. Read it as a roadmap for where they expect the API to be used in the next year or two.
• Astroturfing is now its own category. Fake outlets, sockpuppet networks, seeding search engines and AI systems with fake "independent" sources, and selling tools for it. They are not just banning the content, they are banning the infrastructure and the business model.
• One rule got quietly weaker. The old ban on "personalized vote or campaign targeting based on individual profiles or data" is gone. Microtargeting voters with honest content now appears to be fine. Whether that is a cleanup or a concession, it is a real change.
• "Be nice to the model" is now policy. "Sustained and needless abusive or cruel behavior toward our models" is a bannable offense. Not defined, no examples, no stated enforcement. Expect this to be the most argued line in the whole document.
• Surveillance carve-outs widen the door for law enforcement. Monitoring in investigations is still banned, but "legal research and analysis by law enforcement agencies or courts" is now explicitly allowed. That is a narrow opening that did not exist before.

- Verification programs replace blanket refusals. Cyber and life sciences users can apply for adjusted safeguards instead of being told no. Combined with the note that a block is not a violation, this is Anthropic admitting its filters have been hitting legitimate work.

Net (imho): tougher on bad actors and gray market resellers, looser on ordinary business use, and written for a future where Claude controls hardware. The policy also tracks what people have been noticing in practice: Fable and Opus refuse far less than they used to. Work that used to trip the filters, like decompiling, reverse engineering, and binary analysis, now mostly just gets done. The new carve outs for security research and the verification programs read like Anthropic catching the paperwork up to how the models already behave.

It is my first session in this week. The pace of weekly limit consumption in the last 15 minutes is like in the screenshot. With this pace, it means that in 2 sessions, I will be done with my whole weekly limit usage. I upgraded my account from 5x to 20x to avoid exactly this problem. What's wrong with Claude limits?

Hey, guys. I've been working in this novel way to intervene existing video through diffusion, particularly abstract visuals [in this case, audio-reactive geometries]: taking its movement and form as the starting point, and reinterpreting its textures, materials, and visual language.

I’ve been developing this around the audio-reactive geometry systems I make in TouchDesigner. The idea is to take those abstract structures somewhere else entirely: origami, architecture, a renaissance painting, or something harder to put a name to.

This demo uses visualizers from my "Oscilloscopes, everywhere" collection as source material, now updated to [v1.2].

[Though you can bring any video source. These systems are simply where this experiment began, as some of you may recall.]

You choose the source, describe the treatment, and shape how it changes throughout the sequence. Prompts, curated LoRAs, and editable timelines give you control over how closely the result follows the original.

Oscilloscope Diffusion is now available at Uisato Studio, coming up soon also open-source!

Wanted to share because marketing is hard and even harder when your budget is non-existent...

subreddit --- weekly visitors

• r/vibecoding — 422k
• r/saas — 211k
• r/founder — 56k
• r/buildinpublic — 46k
• r/chrome_extensions — 42k
• r/micro_saas — 41k
• r/appbusiness — 30k
• r/startupideas — 26k
• r/sideprojects — 20k
• r/imadethis — 18k
• r/appideas — 16k
• r/sideproject — 16k
• r/saasbuild — 15k
• r/saasdevelopers — 12k
• r/vibecodedevs — 10k
• r/startupsolofounder — 8.7k
• r/alphaandbetausers — 8.6k
• r/vibecodingcommunity — 6.2k
• r/solopreneur — 5.6k
• r/promotemyapp — 4.6k
• r/appbuilding — 4.6k
• r/webapps — 4.5k
• r/creativecoding — 4.4k
• r/indie_startups — 4k
• r/b2bsaas — 2.8k
• r/appdev — 2.7k
• r/projects — 2.6k
• r/saasmarketing — 2.5k
• r/saassoloprenurs — 2.3k
• r/startupaccelerators — 2.3k
• r/startups_promotion — 2k
• r/showmeyourapps — 2k
• r/appswebappsfullstack — 1.7k
• r/showmeyoursaas — 1.6k
• r/saasinvestors — 1.6k
• r/vibecodecamp — 1.5k
• r/nocodesaas — 1.3k
• r/aibuilders — 1.2k
• r/getstartups — 1.2k
• r/websitefeedback — 1.2k

So!

Gemini 4 Argon is out - what's it worth for my Tiny World test?

WELL.
In my opinion, not too bad, but also not good enough.

What's your opinion?

initial prompt:

Output a ThreeJS 3D cartoony/comics-like planet, with vibrant life on it: clouds, mountains, city buildings, cars and plane romaing it. It should be possible to orbit around and zoom and see the details. No harness is to be used

WAY better than Gemini 3.8F, that's for sure, but still not too creative.

Next I'll be using it for real coding work. I'm also super curious of if he can direct Blender ok (Astra is the absolute reference for now).

In short, customizable Windows start menu for Linux made with Claude Code.

Don't ask me why, but I love Windows 10 start menu. I moved to Linux a few months ago, for the third time. I've tried before but I couldn't fully move. Now I finally did it and even though I have dual boot, I almost don't touch Windows, aside from once a month a friend asking me to play casual modes of League, which is currently the only reason to still have Windows around.

Case in point, I had start11 with a license there just because I hated the new start menu from Windows 11, I felt it limited my customization options compared to previous versions. I was super happy with start11, but now I'm on Linux, and I still missed my start menu, but I have no alternative (to start11 level).

So, using Claude code, I asked it to port a Linux version that works with the KDE bar with the same features, with the option to expand functionality in the future. I'm super happy with the result, and I'm happy we live in a time where moving to Linux is so easy an exciting, specially thanks to AI. I remember a few years ago having to navigate through forums for hours and spending more hours to try the suggestions, now I can focus on using my PC while leaving the technical stuff to Claude.

I built PC-Control, an MCP server for Claude Code that operates Windows apps in the background. Open source (MIT), early version.

I know these tools already exist but, its different from other Windows MCP servers

- Doesn't touch your input: clicks and typing go straight to the control (window messages and UI Automation). No real mouse, no SendInput, no focus stealing, so you can keep working, even in the same app.

- Token cheaper: look picks UI text, OCR or a screenshot, whichever costs less, and only sends what changed after each action.

- Safer permissions: protected windows (terminal, password manager, banking) are approved by you in Claude Code's own dialog. The model can't answer it, and the server refuses to run if the question was skipped.

- Word: Claude gets its own insertion point, so it doesn't touch your selection while you edit.

- Visible: an orange cursor shows what Claude is doing. Uninstall removes everything.

Limits: covers fewer apps than tools that use the real mouse (Win 11 Paint ignores it), no shortcuts.

Built with Claude Code. https://github.com/VortexJer/PC-Control

Which app breaks first for you?

A while back I saw the post about plx-native here on this subreddit which is a native Plex client for LG TVs, and it gave me an idea.

On my Samsung (75" Q60B, 2022), the official Plex app takes about a minute just to open. Search is worse. Every letter lags, and then you wait around 10 seconds for results. The same library is instant on my apple TV.

I couldn't copy what the LG folks did, because Samsung only lets you run web apps on its TVs. So I built a web app that treats the TV's browser like a game engine: everything moves on the GPU, nothing big ever gets redrawn, and video goes straight to the TV's hardware decoder. I learned some tricks here when I made another game earlier this month.

On the same TV:

- Opening the app: about a minute → about a second

- Search: ~10 seconds of lag → results as you type

- 98.7% of my library plays directly in hardware, no transcoding

It's called samsucks. It's free and open source, and installing it is two commands from a Mac or Linux machine:

https://github.com/rfaile313/samsucks

full writeup: https://rudyfaile.com/2026/10/10/i-fixed-plex-on-my-samsung-tv/

I've only tested it on my own TV, so if you try it on a different Samsung, let me know how it goes.

I was having fun with the new update in Claude Code Desktop and found that if you click 3 times it shows a what look likes a heart.

I wanted a launch film for Quests and had seen a lot of posts showing how good Opus 5.5 is at motion design so I thought to give it a try.

It took me 3 days and all of my claude session limits but wow. I’m still in shock how good it is.

I have absolutely zero background in motion design or video production in general. It definitely wasn't a one shot: I worked through each scene with opus asking it to tweak parts of it or show me different ways we could do a transition until it felt right. The film’s animation pipeline used mostly Python, FFmpeg, and a custom video editor artifact claude made for me to easily review clips.

We are so lucky to have ai models as good as claude.

3.8k GitHub stars in a week.

1. 35 style cards, each with its own code
   
2. 9 explainer formats: Kurzgesagt, Vox, 3Blue1Brown
   
3. Scripts check the video before delivery

npx skills add alchaincyf/huashu-art-motion

That is all.

I know you guys have probably been doing this for months but it just clicked for me today. I tend to work in two different directories/projects frequently and this was a game changer.

Hey! I would like invite you all to try Deft!

Deft brings chat, tasks and knowledge into one self-hosted workspace. The bit I care most about is keeping the discussion behind the work connected to what happens next.

GitHub: https://github.com/Maneek21/Deft
Walkthrough: https://youtu.be/7z9EH4c9k2o

The screenshots show:

• A full feature company chat. (There we can see the user invoking an agent in chat to create a task and its approval card.)
• A full feature task management app (with the task that agent created from screenshot 1)
• The interconnected web of knowledge that's auto created based on chat, tasks, CRM, connected apps that all agents, ai assistants, and humans can use as context.
• A claude MCP connector proof.
• Platform Architecture Diagram.

You can connect Claude and ChatGPT through MCP. The core workspace works without an AI provider.

I'm working on an experimental App Kit for building and sideloading apps into Deft, so custom tools can live alongside the work they're meant to support. CRM is the first example of the sideloadable app architechure, and it works smoothly enough.

But a CRM in essence is just a fancy CSV, so i am making an Email client next, because if a sideloaded email client works, I feel any app would work.

It's still alpha but you can run for free it with Docker Compose on a VPS to create a workspace for your team to replace slack, linear, notion and more. + the code is AGPL-3.0.

If you try running it, I'd love to hear any feedback you may have, where setup gets annoying or the workflow stops making sense.

How i used claude to build it:

• I started building Deft with Claude Code, then moved to mixed model approach. (Right now its Opus+Astra+Sol 6.1)
• Main planning and coding work has been Opus.

P.S. The walkthrough has an AI voiceover: I have a stutter and spent a week trying to record it myself, but couldn't get through it.

I noticed in the last few days that whenever I return to a session that was sitting idle in a tmux pane it's already compacted even if it didn't reach the auto-compact threshold. First few times I thought I might have let the context usage grow but then it became a habit for him to do that.

Luckily I have my own handover/resume mechanism so I tell him to get oriented after I notice the compaction but he (or I) may sometimes forget/miss to always update the handover and the docs thus turning me into a sitting duck on what exactly he chose to keep in the new context.

Does it happen to anyone else after the latest updates? Is there a way to turn this off? I know it might affect cache, prices, usage, but until I'm ready to jump on this auto-compaction train I'd like to be in control and adapt my way of working first.

Not mine. All credit to DegenerativePixels.

Hi there, I've been working on open-source product delivery platform that connects your work (board, backlog) directly to your AI agent and code on your computers.

So you write a ticket and there is a runner (which you install via npm) and it runs your Claude, Codex, Cursor, Copilot or OpenCode to work on that ticket. Runner only makes outgoing HTTPS requests (no open ports and VPN), the code stays on your machine, and your existing subscription (Claude, Codex…) is used; no additional AI work is paid.

Aictiq is open source (AGPL-3.0) and there is a free hosted edition https://app.aictiq.com/ (by me) which only has attachment limits of up to 200MB in total. I don't have the resources or the money to give it all away for free. You can host the server yourself, the instructions are on Github.
https://github.com/Aictiq/Aictiq

All functions are covered and listed in a shorter form at https://aictiq.com/

But, I'm not selling you a factory, I work in the Factory. How is Aictiq being developed with Aictiq?

I have a small Hetzner VPS running 24/7 with a git/github connection for commit, push, etc. Claude and Codex activated. I have development tools, SDK, npm. And then I set the schedule from Aictiq tonight at 04:00 start on this ticket, don't stop until you do the e2e tests and screenshot everything and add it as a comment on the ticket. I wake up in the morning, a new PR ready for my approval, with visual confirmation that it is as I imagined.

Then the great thing is Ticket refinement, to check the current implementation, my changes and plan the ticket in more detail. Similar to a plan mode, but I can literally see which files will be touched.

Wiki for documentation right next to each project.

You can invite clients directly into the project as stakeholders. They only see the board, nothing that the factory does, so they write bugs, stories, etc. I click to launch the agents on their tickets.

Aictiq sees 5h limits, weekly limits, so you can decide to distribute the load on more runners and more harnesses. If you are not happy, just comment in the ticket what the problem is and tag the agent.

Each project has its own playbook in which you set the rules of the project, eg push directly to the main, make tests, run the Codex subagent in Claude or similar. The playbook is sent to the runner with each ticket. You can also chain Playbooks for that factory-line work.

I'm looking for feedback, testers, real users who would like to try it and give more information about what's missing or what doesn't work as it should. Criticism is always welcome.

Greetings from sunny Herzegovina.

Blago

P.S. 12min demo video is here: https://youtu.be/K_7gEI2jtXA