Amicode
Your open autonomous research interface.
Run the loop
Autonomous research demo
Amico takes on the Unitary Foundation QEC challenge — the whole loop, hypothesize to decide, with no human between rounds.
Ask Amico anything, / for commands, @ for context …
Open autonomous research
Optimize an X gate on my trans
Amico authors a self-contained Piccolo.jl optimization from plain language, runs it, and streams the result to native panels. A short guided exchange settles parameters before code is committed, and you can stop a solve in flight.
Live execution and versioned memory
Warm-start from our best 24 ns X gate and beat it
Ask Amico anything, / for commands, @ for context …
The Run Inspector overlays pulse plots and traces fidelity and constraint violation as they fall. The pulse catalog keeps a warm-startable, versioned library of your best pulses and promotes when you beat the incumbent.
Straight to hardware
Play this pulse on the board
- RFSoC boardmetalconnected
- Pure-Julia mockmockno hardware
Ask Amico anything, / for commands, @ for context …
Drive real RFSoC boards through IntonatoQICK.jl over a coarse three-verb boundary — upload_pulse!, trigger!, readout — or run the entire closed loop against a pure-Julia mock with no hardware at all. Same script, mock or metal.
The knowledge
Vaults — your knowledge, mounted
What do we already know about gate duration on Q2?
- Personal
- your notes · local
- Team
- shared specs · team
- Project
- package knowledge · public
Reading across all three — 3 notes and 41 runs mention Q2 and duration.
Ask Amico anything, / for commands, @ for context …
Personal, team and project vaults stack under ~/.amico/vaults and become first-class context the assistant plans against. Works fully offline; scales to a team with local, team and public visibility and PR-based promotion.
Fleet management — one logical studio across machines
I'm on the laptop now — is my work here?
- workstationhostcanonical
- laptophostthis machine
- lab-boxhostreachable
- Vaults
- in sync
- Chat
- canonical DB
- Work in progress
- 2 files
Ask Amico anything, / for commands, @ for context …
Vault sync, a canonical chat database, and work in progress that follows you between hosts over an SSH mesh. When the canonical is unreachable you keep working locally and rejoin merges it back.
The foundation
Open system management, not just a chat panel
What's in my system right now?
- Workspace
- what you edit
- ~/.amico
- what the system manages
- Vault tree
- 3 vaults mounted
- Run Inspector
- 41 runs
- Catalog
- 12 pulses
- Device Inspector
- 4 devices
Each renders managed state semantically, rather than as a file tree.
Ask Amico anything, / for commands, @ for context …
The workspace is what you edit; ~/.amico is what the system manages. Vault tree, Run Inspector, Catalog and Device Inspector render managed state semantically instead of as file trees.
Physics that ships with the tool
Set this up for fluxonium instead
- Rydbergatomsreference
- Transmoncircuitreference
- Fluxoniumcircuitreference
- Trapped ionionsreference
- Bosonicmodesreference
- Hamiltonian
- fluxonium, 3 levels
- Drive convention
- flux + charge
- Units
- GHz · ns
Written into x_gate_flx1.jl itself — the script carries its own physics.
Ask Amico anything, / for commands, @ for context …
Platform references for Rydberg, transmon, fluxonium, trapped-ion and bosonic systems inline the Hamiltonians and drive conventions into each script, so it stands alone.
Skills are the product
Which skills do I have here?
- transmon
- fluxonium
- atoms
- ions
- bosonic
- solve
- calibrate
- benchmark
- warm-start
- catalog
- vault
- fleet
- From your vaults
- 6 skills
- From Julia packages
- 4 skills
- Behind entitlements
- 2 skills
All versioned with the extension, so a workspace can be pinned to a release.
Ask Amico anything, / for commands, @ for context …
A growing library of public skills ships in the extension, versioned with it. Your own vault mounts and Julia-package skills layer on top behind entitlements.
The interface of the loop
Every capability on this page is one face of the same loop — authored here, run on hardware, read back into memory. The loop is built to close on real hardware at the speed quantum turns, and to carry past the first domain. See the system it serves