~
Docs
CoursesLanguageSystemUserspaceToolsManualGlossary
AgentAmesAPIAquaArmArvoAtomAuraAural ASCIIAxesAxisAzimuthBatteryBehnBowlBridgeBuntCardCaseCaskCellCensuresClaimsClamClayCold atomCometCommitConsContextCordCoreCueDelegated SendingDeskDillDocument ProposalDojoDoorDouble-bootDry GateDuctEclipticEntropyEvent LogEyreFaceFactFoo Bar BazGalaxyGallGardenGateGeneratorGiftGlobHD WalletHeadHelmHoodHoonInvite TreeIrisJaelJamJetKelvin versioningKernelKeyfileKeywordsKhanKilnLandscapeLarkLegLickListLoobeanLullMarkMetalsMoldMonadMoonMoveNockNoun~OTA UpdatesPath PrefixPath@pPayloadPeekpHPierPillPlanetPokeProxiesScryReplayFactory ResetRollerNaive rollupsRuneRuntimeSailSampleScrySenateShipSlamSpiderSponsorStarStringSubject Oriented ProgrammingSubjectSubscriptionTailTapeTermThreadTrapUdonUpgrade ProposalUserspaceVaneVaseVereVotingWarm atomWet GateWingWireWrapper~zodZuse
Glossary/Agent

Agent

Agents are the main kind of userspace application on Urbit. They have a persistent state and API that handles events and produces effects. Agents are managed by the Gall vane (kernel module). Agents are sometimes just called "apps", though that is a little ambiguous as a single app installed in Landscape may have multiple agents working together in the background.

Gall agents can variously be treated as databases with developer-defined logic, services, daemons, or a kind of state machine.

Further Reading

  • App School: A comprehensive guide to writing Gall agents.
~Urbit Docs
HomeCoursesLanguageSystemUserspaceToolsManualGlossary
GitHubAirlock APIsUrbit BinariesDeveloper Mailing ListIssue TrackerWhitepaper
Privacy Policy
Terms of Service
[email protected]