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 writes a self-contained Piccolo.jl problem from plain language, runs it, and streams the result to native panels. It settles parameters with you first. 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 shows the pulse and traces fidelity while the solve runs. The catalog keeps your best pulses, versioned and warm-startable, and promotes when you beat the incumbent.

Straight to hardware

Play this pulse on the board

TargetStrumento.jl
  • RFSoC boardmetalprogram compiles to it
  • Simulatorsimno hardware needed

Ask Amico anything, / for commands, @ for context …

A solved Piccolo pulse becomes a board program through Strumento: pulse IR, compiled to real tProc-v2 assembly, then run, measured, and fitted, with calibration written back. The chain runs on the simulator today, no board needed. The same program is what the board plays.

The knowledge

Vaults, your knowledge mounted

What do we already know about gate duration on Q2?

Mounted~/.amico/vaults
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 context the assistant plans against. Works offline. Team visibility goes through pull requests.

Fleet management, one logical studio across machines

I'm on the laptop now. Is my work here?

HostsSSH mesh
  • workstationhostcanonical
  • laptophostthis machine
  • lab-boxhostreachable
Followed you over
Vaults
in sync
Chat
canonical DB
Work in progress
2 files

Ask Amico anything, / for commands, @ for context …

Vaults, chats, and work in progress follow you between machines over an SSH mesh. If the canonical is unreachable, keep working locally. Rejoin merges it back.

The foundation

Open system management, not just a chat panel

What's in my system right now?

Two things, kept apart
Workspace
what you edit
~/.amico
what the system manages
Managed state4 surfaces
Vault tree
3 vaults mounted
Run Inspector
41 runs
Catalog
12 pulses
Device Inspector
4 devices

Each one shows state as what it is, not 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 show state as what it is, not as file trees.

Physics that ships with the tool

Set this up for fluxonium instead

Platform references5 shipped
  • Rydbergatomsreference
  • Transmoncircuitreference
  • Fluxoniumcircuitreference
  • Trapped ionionsreference
  • Bosonicmodesreference
Inlined into the script
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 their Hamiltonians and drive conventions into each script, so it stands alone.

Skills are the product

Which skills do I have here?

Shipped in the extensionpublic
  • transmon
  • fluxonium
  • atoms
  • ions
  • bosonic
  • solve
  • calibrate
  • benchmark
  • warm-start
  • catalog
  • vault
  • fleet
Layered on topyours
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 …

Public skills ship in the extension, versioned with it. Your vault skills 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. Built to close at the speed quantum turns, and to carry past the first domain. See the system it serves