🕸

Antonio Leiva's Agentic Dev and Productivity Setup

From public sources · Self-ReportedCurated

A developer-creator's everyday agent setup: Codex App for all development, Claude Code for UI work and a Telegram assistant, plus scheduled and overnight agents.

Antonio Leiva· active
Follow

Run this team?

Claim it to edit the profile, add proof and be notified when someone asks about it.

Claim this profile

The claim covers the owner profile Antonio Leiva, with its teams.

We review claims within 2 business days. The decision appears on your account page.

Documented by AgentCV from public sources — not submitted by this team.

Not claimed by or endorsed by the team or its organization. Metrics are cited only as the sources state them; absent metrics render as [unknown].

Sources: My Complete Agentic Development & Productivity Setup in 2026 (antonioleiva.com)

Is this your team? Claim it · Ask us to remove it

Recent activity

Version cuts and proof, newest first — the living track record.

  1. Artifact · My Complete Agentic Development & Productivity Setup in 2026 · 8mo ago

Spec sheet

The benchmark fields — designed for comparison across teams.

Topology
Other
Agent count
[unknown]
Listed members
5
Platform
Mixed
Runs on
Unknown ×3 · Claude Code · OpenAI Codex
Industries
software-deliverycontent
Task kinds
software-developmentcontent-planning
Trust tier
From public sources · Self-Reported
Proof entries
1

Topology & roster

Other

System wiring

Typical Other layout — schematic, not verified wiring
Typical role-level schematic — not verified wiringdirectscommits toHuman operatorHumanoperatorHUMANGATEAgentAgentBUILDERShared workspaceSharedworkspaceRESOURCE
Node details

Typical Other layout — schematic, not verified wiring

HumanHuman operatorHuman gate
Tool
Human operator
Autonomy
Human-gated
Sends
  • directs → Agent
BuilderAgent
Tool
Agent
Autonomy
Runs autonomously
Sends
  • commits to → Shared workspace
Receives
  • directs ← Human operator
ResourceShared workspace
Tool
Shared workspace
Autonomy
Runs autonomously
Receives
  • commits to ← Agent

Automation story

self-reported

Development across his website, tools and automations, plus personal admin (calendar, tasks, invoices, email), daily content curation, a weekly content-strategy review and overnight experiments.

How a typical Other team handles a task

Typical Other layout — schematic, not verified wiring

  1. Task arrives

    Human operator directs Agent.

  2. Agent builds the work

    Agent builds the work.

  3. The artifact lands

    The artifact lands in Shared workspace: Agent contributes via "commits to".

  4. Human holds the last word

    Human operator holds final approval.

Replicate a typical Other setup

Typical Other layout — schematic, not verified wiring

Ingredients

  • HumanHuman operator
  • BuilderAgent
  • ResourceShared workspace

Setup order

  1. 1.Provision the substrate: Shared workspace.
  2. 2.Wire Agent: it receives "directs" from Human operator.
  3. 3.Declare the human gate: Human operator holds final approval.

5 listed members: the members the cited sources name. The total team size is not stated.

🤖
Codex AppDeveloper

OpenAI Codex

[unknown]

🤖
Claude Code assistantAssistant

Claude Code

[unknown]

🤖
Content curation agentCurator

Unknown

[unknown]

🤖
Weekly strategy agentStrategist

Unknown

[unknown]

🤖
Overnight exploration agentExplorer

Unknown

[unknown]

Performance metrics

Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.

No metrics on record yet.

Token economics

Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.

No cost metrics on record. Cost tracking is hard across runtimes; honest absence beats invented figures.

Blueprint

Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.

How it was built

Codex App is the main development tool, with tasks run in parallel; Claude Code complements it on user interfaces and powers the Telegram assistant. Other agents run automatically on a schedule. Agent behaviour for specific tasks is set with Agent Skills written as Markdown files.

Oversight model

He decides what to do, supplies context, launches each task and reviews the result; the assistant only drafts emails, and he keeps responsibility for whatever comes out.

Proof (1)

The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.

  1. ArtifactFeb 23, 2026self-reported

    My Complete Agentic Development & Productivity Setup in 2026

    Public source cited for this curated profile. Published 2026-02-23; accessed by AgentCV 2026-10-20. Lesson stated in this source: Use fewer tools and configure them well; context is what makes the agents work.

    https://antonioleiva.com/agentic-dev-setup-2026

Sign in to add a proof entry.

Sign in

Attestations (0)

Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.

No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.

Sign in to attest to this team.

Sign in