Skyflo Engineering Log
Articles about Skyflo Engineering Log
One Team, One Subscription, Each Person's Work
Team and Team Max bring one organization bill, shared included usage and clear account roles to Skyflo. Each person keeps their own missions, workspaces and memory.
Start Where the Work Will Run
A mission can begin in Skyflo Cloud without cloning its repository on your Mac first. The useful boundary is the mission: its instruction, branch, work and conversation stay together wherever it runs.
The Mission Outlives the Laptop
Skyflo 1.5 introduces Skyflo Cloud: a mission moves from your Mac with its history and uncommitted changes, keeps working while the Mac sleeps, and comes back when it is idle. How the handoff keeps one owner at a time, what the machine holds and what it can reach, and what the work costs.
Approval Belongs to the Command
An agent can understand your permission and still reach the wrong execution path. Skyflo 1.5.1 carries the mission's approval policy to the command and file change itself, while messages from other missions keep their own identity and limits.
A Message Is Not the Person
Skyflo 1.5 lets missions on one Mac message each other, so one coding agent can ask another a question without a person carrying it between windows. The work was deciding what a message from an agent may and may not do.
An Approval You Can Read
Skyflo 1.4.3 changes what a paired phone shows when an agent asks for permission. Testing on a real iPhone, we found it could ask for Face ID on a command it never showed. A signature proves who said yes. It cannot prove they knew what they were agreeing to.
What a Sandbox Has to Protect
Skyflo 1.4.2 fixes three things about the sandbox its agents work in. None of them was an agent writing outside its area. Each was about what that area touches: files the agent never saw, settings another program runs, and tools the person already relies on.
The Phone Decides, the Mac Acts
Skyflo 1.3 lets a phone follow your missions, answer their questions and approve their actions. The design question was never how to put an agent on a phone. It was how to let a phone say yes without letting it do anything.
Take Over, Hand Back
Skyflo 1.4 lets you and an agent share one browser and one terminal. The hard part was not letting a person grab the mouse. It was deciding who owns the surface at every instant, what the agent may see of your turn, and where the mission resumes when you give it back.
A Voice Is a Control Surface
Skyflo 1.2 lets you talk to a mission while it runs, and the voice drives the product rather than describing it. The hard part is not speech recognition. It is deciding, sentence by sentence, whether what you said was work or a control.
Skyflo Improves How It Improves
Skyflo 1.1.0 is the release where the engineering harness becomes a HyperAgent. What that means, the three layers it is built from, and the boundary that keeps a system which changes itself accountable.