I built an agentic engineering system called Citadel.
Not a demo. Not a wrapper.
A system where AI agents can:
1. work in parallel
2. persist progress across sessions
3. pick up where previous agents left off
4. actually complete real engineering work
It’s already being used in production.
~1,000 downloads
~440+ GitHub stars
inbound from developers using it to ship
I’ve been deep in Claude Code, Codex, and multi-agent orchestration while this space is still forming.
This is what I’m focused on:
agentic systems that move beyond “chat” into actual execution
If you’re building in this direction or hiring for it, pay attention.
https://t.co/ZLdlYREXLC
Some of the improvements I've been working on for Citadel, the Operating System for Agents.
1. Local Citadel Control Plane
Added a local operator dashboard path so Citadel state is visible without spelunking files.
2. Fleet DAG and Merge Steward
Added dependency-aware Fleet task parsing and merge readiness checks.
3. Worktree Environment Readiness Profiles
Added readiness reporting so isolated worktrees can be checked before high-autonomy work.
4. Signed Telemetry and Artifact Lineage
Added hash-backed telemetry/artifact lineage and verification.
5. Memory Compiler and Semantic Blocks
Added source-backed memory blocks for reusable project knowledge.
6. Phase Exit Evidence Contracts
Added campaign evidence tables and a validator so phases cannot be marked complete from prose alone.
7. Sandbox Provider Contract
Added an explicit sandbox-provider abstraction with supported worktree behavior and clear unsupported placeholders.
8. Skill and Workflow Packaging Upgrade
Added skill metadata, cataloging, scaffold support, and packaging tests.
9. Thin Runtime Adapter Matrix
Added runtime capability levels and tradeoffs so Citadel clearly says what Claude Code, Codex, OpenAI, or unknown runtimes can and cannot guarantee.
10. Shared Repo Map Substrate
Upgraded `/map` into a reusable `core/map` substrate with file hashes, imports, exports, routes, package scripts, verification commands, scoped slices, and stale checks.
Enhanced Token Info for Citadel will be available on @dexscreener shortly!
Thank you for those that are interested in this sort of vehicle to drive attention and funding to the project.
Less input leading up to the time you want to go to bed helps. Writing whatever comes to your mind is a way to get it out of your head, that can help.
I went on ADHD meds for a small stint of 2ish months, and I experienced all the mental noise collapse into a singular stream, among other things that were helpful and some side effects that weren't.
But when I stopped, I retained the ability to have a quieter mind. I can't really describe to you how to blink or flare your nostrils, but once you do it, it's just something you can do now.
Cuando tenía 20 años, tenía un novio que editaba vídeos en fiverr por cinco dólares.
Cinco dólares, por videos complejos que le tomaban horas hacer.
El plan era simple; iba a hacer los vídeos de cinco dólares con una calidad increíble para llenar su portfolio, conseguir calificaciones de 5 estrellas y poder aumentar los precios una vez tenerlos.
En menos de un año, cobraba 1000 dólares por trabajo.
Quieren saber dónde está ahora? Hizo los efectos especiales del Eternauta y ahora está en Canadá haciendo Godzilla vs Kong. Viaja por todo el mundo trabajando para los mejores estudios de efectos especiales.
You just need to start.
@hyporliquid Someone impersonated my project, I had to sort it out with the team at Bankr and the team at Dex. There is no scam I am running. Apologies for any confusion that they caused.
Important $CITADEL clarification:
The only official/community token connected to me and the Citadel project is:
CA: 0x4dfe9e5dab29209b5f1d9270b22ac54caaadcba3
There is another Citadel token using my project name, repo, graphics, and identity. I did not authorize it, and it is not the official token.
Please verify the CA before trading.
A community token for Citadel was launched on Bankr.
I did not launch it, but I found out because people started tagging me, and I want to be transparent about it.
From what I can see, trading fees are routed to me. If that continues, I’ll treat those fees as support for Citadel and use them to help move the project forward.
Citadel is the project.
It’s open-source infrastructure for Claude Code + Codex: durable project memory, /do command routing, safety hooks, cost tracking, and parallel agent worktrees.
That is where my focus is.
I’m grateful people care enough to rally around it. Attention, testing, feedback, contributors, docs, issue reports, examples, and people explaining the product are all genuinely useful.
I’m also not going to make promises around token price, future value, targets, or outcomes.
The best version of this is simple:
people discover Citadel
people try it
people give feedback
people help improve it
the project gets stronger
If you’re here because of the token, welcome.
The most helpful thing you can do is help make Citadel better.
Read the repo. Try the install. Open issues. Share what confused you. Suggest improvements. Help explain the problem it solves to other builders.
Citadel repo:
https://t.co/ZLdlYREXLC
The project comes first, and I appreciate the support.
I’m building Citadel, an open-source orchestration layer for Claude Code + Codex.
It gives agentic coding workflows a real operating layer:
• one-paste install
• /do setup --express
• durable project memory
• /do command routing
• safety hooks
• cost tracking
• parallel agents in isolated worktrees
The goal is to make AI coding agents easier to coordinate across real projects, not just one-off chats.
Repo:
https://t.co/ZLdlYREXLC
A community token for Citadel was launched on Bankr.
I did not launch it, but I found out because people started tagging me, and I want to be transparent about it.
From what I can see, trading fees are routed to me. If that continues, I’ll treat those fees as support for Citadel and use them to help move the project forward.
Citadel is the project.
It’s open-source infrastructure for Claude Code + Codex: durable project memory, /do command routing, safety hooks, cost tracking, and parallel agent worktrees.
That is where my focus is.
I’m grateful people care enough to rally around it. Attention, testing, feedback, contributors, docs, issue reports, examples, and people explaining the product are all genuinely useful.
I’m also not going to make promises around token price, future value, targets, or outcomes.
The best version of this is simple:
people discover Citadel
people try it
people give feedback
people help improve it
the project gets stronger
If you’re here because of the token, welcome.
The most helpful thing you can do is help make Citadel better.
Read the repo. Try the install. Open issues. Share what confused you. Suggest improvements. Help explain the problem it solves to other builders.
Citadel repo:
https://t.co/ZLdlYREXLC
The project comes first, and I appreciate the support.
@Drip_Official_ I burned my tokens so the community didn't see a bag holding over their head that I could rug pull, but if that wasn't the right move you'll have to forgive my naivety 🫡
Right now I’m treating Citadel as open-source first. The immediate goal is adoption, feedback, and proving that developers actually want this workflow.
Longer term, I see monetization through a few paths:
1. Hosted Citadel for teams
2. Paid team/workspace features
3. Enterprise support and setup
4. Templates, integrations, and managed agent workflows
5. Consulting around agent infrastructure
So the short-term focus is trust and usage.