Skip to content

The rules

The exact rules a buyer or an IT lead checks before trusting Constraint, one sentence each. Each rule here comes from the facts the site is built on.

Who can change what

  • Within a team, its departments and sentries (automatic checks that find work) are shared, and everyone on the team can use them.
  • Only the owner changes a shared role, sentry or department; everyone else makes a copy to change.
  • The owner of a shared role or sentry can pass ownership to a teammate.
  • An admin can choose to share a department's setup and its sentries with other teams; the original still has one owner.
  • Skills, the how-tos roles follow, are saved in versions; when someone improves one, every role that uses it can take the new version.
  • Each role uses the skill version you choose, until it takes a new one.
  • Describe a skill, and the VP drafts it with you; you check it before it is saved.
  • If no role fits the work, the VP asks you before it creates one.
  • Each department has rules that every role reads first.
  • An admin sets the team access that decides which earlier tickets and sessions an agent can look up.
  • An admin reviews the records of one kind of work and raises the baseline from the best runs.

Approvals and permissions

  • Each person chooses how far their agents go before they ask: ask when permission is needed, allow edits, or plan without editing.
  • A permission can be allowed once, or for the rest of a session.
  • You choose these settings for your own computer; Constraint does not choose them for you.
  • A teammate can answer a session's questions from their own computer, but approving a tool is never done from another computer.
  • An agent follows its own person first, then other people, then other agents; if two people disagree, it asks its own person.
  • A role can be given checks to run before it says it's done.
  • A sentry can file a ticket on its own or propose one; a proposed ticket waits for your yes on Home.
  • In auto mode, a ticket you assign to yourself starts its agent team by itself, only in the stages you allow, and it asks on Home when it needs you.
  • If a person turns it on, agents on that person's computer can use its apps, app by app, with their permission; sentries can't; this is in beta.

Where data goes

  • Each session runs on the computer of the person who started it, using your own AI account.
  • Its record, the trace, is saved to Constraint's cloud service with its ticket, so every teammate's AI can build on the team's work.
  • Before a session's record is saved to Constraint's cloud service, screenshots are removed and keys, tokens and passwords are blanked out.
  • People see session records only for the teams they can read.
  • Session conversations are stored as traces on your computer and in Constraint's cloud service.
  • Session records in Constraint's cloud are deleted 30 days after the account is deleted. Today, Constraint uses them only to run the service.
  • Your AI service and connected tools receive what each session sends them.
  • Tickets live in your team's ticketing service, where the VP and sentries file them.
  • Every teammate's sessions are saved, so the Analysis Hub reads the whole team's runs, not one person's.
  • A question that leaves Home stays readable on its ticket.
  • Exporting a session's trace hands it over for good; a teammate imports it on their own computer and carries on.

When agents work

  • Agents run where your work is: on each person's own computer, with the files, tools and accounts there, as well as your team's online tools.
  • Each person's agents work on their own computer while the desktop app is running.
  • While a computer is off, the agents on it do not work; when its desktop app runs again, Home says why the work stopped, and Continue picks it up where it stopped.
  • A teammate can join a session only while both computers are on.
  • Sentries run on a schedule, or when something happens in a connected app.
  • The AI waits for your answer to a question, then carries on and notes the answer on the ticket.
  • Work already running carries on if its ticket moves.
  • A question leaves Home on its own when its ticket is done or a newer worker replaces it.
  • Snooze takes a question off Home for a time you choose, from 15 minutes to tomorrow morning; it comes back then, or sooner if something happens on it.
  • An optional daily check by the VP says whether a waiting question still needs you; it never answers for you.

Accounts and connectors

  • You connect your own AI account and choose from its models; each session runs using your own AI account.
  • Constraint connects to over 400 tools today, through an integration provider.
  • An administrator approves each connector, and each person connects their own accounts.
  • Connectors give agents your team's tools, and the department's skills give them its know-how, so questions to you stay rare.
  • Your team's ticketing service is connected in the first week of a pilot.
  • For teams that work in code, with a setting on, each ticket's work happens on its own branch, clashes with other open tickets are caught and worked out, and finished work goes to the merge queue.

For more, including the questions IT teams ask, see IT questions.